Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
[Sorry, should have gone to the list as well] Steve Kinney (ad...@pilobilus.net) wrote: > Here's what my installation looks like when starting up, in case > it's of any use: > > ~ $ gimp --verbose > INIT: gimp_load_config [...] > INIT: gimp_real_restore > Parsing '/home/yeti/.gimp-2.8/pluginrc' Plugin querying would happen here. If you want to experiment you can just remove the pluginrc, gimp then re-queries all the plugins. But apparently this is not the cause for your slowdown. Try the following: In the "moreutils"-Package there is a small utility called "ts" (for TimeStamp). Then start Gimp like this: $ gimp --verbose 2>&1 | ts -s [%.S] ts then prefixes every line with a timestamp relative to the starting time. That way you could try to figure out where the time is lost. Bye, Simon -- si...@budig.de http://simon.budig.de/ ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
On 12/18/2015 02:40 PM, Simon Budig wrote: Actually querying is usually not happening (except on the first startup, then querying the plugins really is a drag). However, there have been reports, that under some circumstances all plugins get re-queried, AFAIK it is not clear what might cause this. On my old (ten-year-old) computer modifying the source code to not compile the plug-ins made a big difference in compile time, and also in start-up time. FWIW I'm pretty sure startup time with fewer plugins was always quicker, even when I hadn't just finished rebuilding GIMP. Elle ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
On 12/18/2015 03:42 PM, Owen Cook wrote: > > Another thing you can try is starting gimp on the command line, # gimp -cfs > for example That seems to start it a few seconds faster, but then that might have as much to do with available system memory, other processes making file system calls, etc. as with anything else. I just posted the output of $ gimp --verbose elsewhere in this thread, in case anyone here might find something useful in there. I got nothing to compare it to myself... But again, I have not seen a substantial difference in start-up time across a variety of versions and platforms from GIMP 2.6 on Windows XP through the current stable version on Mint 17. :o) ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
On 12/18/2015 02:40 PM, Simon Budig wrote: > Elle Stone (ellest...@ninedegreesbelow.com) wrote: >> So the many default GIMP plug-ins can be added to the list of things that >> cause GIMP to take longer to load, that it might be nice for users to have >> the option to not load. > > Regarding plugins: querying them (i.e. starting and asking them what > their procedures look like) is expensive. Gimp queries plugins, when the > plugin is "new" to gimp or its modification date differs from the cached > results of an earlier query. > > So basically Gimp stat()'s plugins on each start, but that is not an > expensive operation (at least not on linux on a local file system). > > Actually querying is usually not happening (except on the first startup, > then querying the plugins really is a drag). > > However, there have been reports, that under some circumstances all > plugins get re-queried, AFAIK it is not clear what might cause this. Here's what my installation looks like when starting up, in case it's of any use: ~ $ gimp --verbose INIT: gimp_load_config Parsing '/home/yeti/.gimp-2.8/unitrc' Parsing '/etc/gimp/2.0/gimprc' Parsing '/home/yeti/.gimp-2.8/gimprc' gimp_composite: verbose=no Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis Adding theme 'Default' (/usr/share/gimp/2.0/themes/Default) Adding theme 'Small' (/usr/share/gimp/2.0/themes/Small) Writing '/home/yeti/.gimp-2.8/themerc' Trying splash '/home/yeti/.gimp-2.8/gimp-splash.png' ... failed Trying splash '/usr/share/gimp/2.0/images/gimp-splash.png' ... OK INIT: gimp_initialize INIT: gimp_real_initialize INIT: gui_initialize_after_callback INIT: gimp_restore Parsing '/home/yeti/.gimp-2.8/parasiterc' Loading 'brush factory' data Loading 'dynamics factory' data Loading 'pattern factory' data Loading 'palette factory' data Loading 'gradient factory' data Loading fonts Loading 'tool preset factory' data Parsing '/home/yeti/.gimp-2.8/templaterc' Parsing '/home/yeti/.gimp-2.8/modulerc' Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-lcms.so' Unloading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-lcms.so' Loading module '/usr/lib/gimp/2.0/modules/libcolor-selector-water.so' Unloading module '/usr/lib/gimp/2.0/modules/libcolor-selector-water.so' Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-high-contrast.so' Unloading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-high-contrast.so' Loading module '/usr/lib/gimp/2.0/modules/libcontroller-linux-input.so' Unloading module '/usr/lib/gimp/2.0/modules/libcontroller-linux-input.so' Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-gamma.so' Unloading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-gamma.so' Loading module '/usr/lib/gimp/2.0/modules/libcolor-selector-wheel.so' Unloading module '/usr/lib/gimp/2.0/modules/libcolor-selector-wheel.so' Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-color-blind.so' Unloading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-color-blind.so' Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-proof.so' Unloading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-proof.so' Loading module '/usr/lib/gimp/2.0/modules/libcontroller-midi.so' Unloading module '/usr/lib/gimp/2.0/modules/libcontroller-midi.so' Loading module '/usr/lib/gimp/2.0/modules/libcolor-selector-cmyk.so' Unloading module '/usr/lib/gimp/2.0/modules/libcolor-selector-cmyk.so' INIT: gui_restore_callback clipboard: writable pixbuf format: image/png clipboard: writable pixbuf format: image/bmp clipboard: writable pixbuf format: image/x-bmp clipboard: writable pixbuf format: image/x-MS-bmp clipboard: writable pixbuf format: image/x-icon clipboard: writable pixbuf format: image/x-ico clipboard: writable pixbuf format: image/x-win-bitmap clipboard: writable pixbuf format: image/tiff clipboard: writable pixbuf format: image/jpeg Parsing '/home/yeti/.gimp-2.8/sessionrc' Parsing '/home/yeti/.gimp-2.8/dockrc' Parsing '/home/yeti/.gimp-2.8/toolrc' Parsing '/home/yeti/.gimp-2.8/contextrc' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-rect-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-ellipse-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-free-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-fuzzy-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-by-color-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-iscissors-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-foreground-select-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-vector-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-color-picker-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-zoom-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-measure-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-move-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-align-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-crop-tool' Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-rotate-tool
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
> > On 12/17/2015 10:21 PM, Steve Kinney wrote: > > > Presently using GIMIP 2.8.10 on Linux Mint. The slow startup due to > > rescan of all plugins & etc. is a feature, not a bug; I have > > observed it across all the versions on all platforms I have used. > > Can we get some absolute numbers? Another thing you can try is starting gimp on the command line, # gimp -cfs for example Owen ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
Elle Stone (ellest...@ninedegreesbelow.com) wrote: > So the many default GIMP plug-ins can be added to the list of things that > cause GIMP to take longer to load, that it might be nice for users to have > the option to not load. Regarding plugins: querying them (i.e. starting and asking them what their procedures look like) is expensive. Gimp queries plugins, when the plugin is "new" to gimp or its modification date differs from the cached results of an earlier query. So basically Gimp stat()'s plugins on each start, but that is not an expensive operation (at least not on linux on a local file system). Actually querying is usually not happening (except on the first startup, then querying the plugins really is a drag). However, there have been reports, that under some circumstances all plugins get re-queried, AFAIK it is not clear what might cause this. Bye, Simon -- si...@budig.de http://simon.budig.de/ ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
On 12/18/2015 07:20 AM, Michael Schumacher wrote: >> Gesendet: Freitag, 18. Dezember 2015 um 06:53 Uhr >> Here's the reason: >> >> 172 brushes >> 112 script-fu scripts >> 92 fonts >> 1 python plugin > > You write "reason". Got any profiling data that supports this and pinpoints > the exact reason for the delay? > > I'm asking because I couldn't claim this myself without that kind of > research, but you might have done it already - you've probably checked > whether startup is faster with less scripts, plug-ins and such, and slower > with more, ... I said that because the GIMP splash screen displays a status area where one can watch its progress in scanning and indexing all the optional components. When that's done, the splash screen closes and the application opens. It's fairly obvious. :o) ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
On 12/18/2015 01:11 PM, Ross Martinek wrote: Bottom line, if you want it to handle like a sports car, don't load it like a dump truck. GIMP comes with a whole lot of default installed plug-ins. I've compiled GIMP from source with most of the plug-ins disabled (there aren't very many "installed by default" plug-ins that I actually use in day-to-day editing). Not only does GIMP start faster, but it compiles faster, too. So the many default GIMP plug-ins can be added to the list of things that cause GIMP to take longer to load, that it might be nice for users to have the option to not load. Elle ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
Different OS: MacBook Pro, 2.66 Ghz intel Core i7, 8 GB 1067 Mhz DDR3, OS 10.6.8, GIMP 2.8 without a lot of bells and whistles: Launch time 4.8 sec. Gimp is like a high performance aircraft, say an F-16. Superbly agile and fast, but when you hang a max loadout of ordinance on it, not so much. So it helps a lot if you know before launch what you will need. In that light, a feature, as an option, (by holding down "Option/Alt/" at launch?) you get presented with a dialog of all the add-ons you have, select those you need. Also comparing GIMP with Photoshop on the same platform, similar "ordinance load," GIMP leaves Adobe products in the mud. Adobe launch times: PS, 20 sec. Illustrator 28 sec. Bottom line, if you want it to handle like a sports car, don't load it like a dump truck. Everything is a trade off. A little thoughtful planning (What tools am I likely to need for this project?) saves a lot of time and frustration. You might have to walk back to the toolshed occasionally, when inspiration strikes, but it was probably time to take a break, anyway. ;^} Ross On Dec 18, 2015, at 6:20 AM, Michael Schumacher wrote: >> Gesendet: Freitag, 18. Dezember 2015 um 06:53 Uhr > >> I just clocked the opening GIMP at 43 seconds flat, on an AMD 64 >> dual core system with 1.5 GB of RAM and Linux 17. This is typical >> of my experience on other platforms with other versions of the GIMP, >> going back at least to GIMP 2.6 on a very adequate office >> workstation running Windows XP. >> >> Here's the reason: >> >> 172 brushes >> 112 script-fu scripts >> 92 fonts >> 1 python plugin > > You write "reason". Got any profiling data that supports this and pinpoints > the exact reason for the delay? > > I'm asking because I couldn't claim this myself without that kind of > research, but you might have done it already - you've probably checked > whether startup is faster with less scripts, plug-ins and such, and slower > with more, ... > > > -- > Regards, > Michael > GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD > ___ > gimp-user-list mailing list > List address:gimp-user-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list > List archives: https://mail.gnome.org/archives/gimp-user-list ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Idea/Request: Fast start mode for GIMP
> Gesendet: Freitag, 18. Dezember 2015 um 06:53 Uhr > I just clocked the opening GIMP at 43 seconds flat, on an AMD 64 > dual core system with 1.5 GB of RAM and Linux 17. This is typical > of my experience on other platforms with other versions of the GIMP, > going back at least to GIMP 2.6 on a very adequate office > workstation running Windows XP. > > Here's the reason: > > 172 brushes > 112 script-fu scripts > 92 fonts > 1 python plugin You write "reason". Got any profiling data that supports this and pinpoints the exact reason for the delay? I'm asking because I couldn't claim this myself without that kind of research, but you might have done it already - you've probably checked whether startup is faster with less scripts, plug-ins and such, and slower with more, ... -- Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
