Liste des Groupes | Revenir à ol advocacy |
-hh wrote this copyrighted missive and expects royalties:I tried launching it again (didn't reboot though) and it came up within 2-3 seconds ... good enough. In retrospect to yesterday, I think the reason why it was "minutes" previously was probably because it had been installed but never launched before, so it had to go through all of its initial setup routines, as illustrated by it searching the entire computer for fonts. Given that I currently have attached ... oops, 12TB of SSDs, plus 46TB of HDDs for backups, that sort of 'go search' task is going to take a chunk of time no matter the OS.
I've not used GIMP for awhile, so I just got a screen recorder runningClean boot on this Lenovo, starting GIMP and killing it as soon as I saw it was
and launched it. It went to go search everywhere for fonts, so after a
minute or two, I killed the recording and let it just continue to run in
the background. Checked back a short while later and it was done; what
really needs to be done to benchmark its launch time is to reboot the
system to start relatively 'clean'. We'll see if I bother...
ready:
$ time gimp
real 0m4.752s
user 0m2.089s
sys 0m0.325s
The "real" time includes loading a shitload of plugins and my reaction time for
seeing the app was completely load and hitting the key to kill gimp.
What kind of slopware are you running git on? MacOS? Windows?
Les messages affichés proviennent d'usenet.