Idea/Request: Fast start mode for GIMP
This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
Idea/Request: Fast start mode for GIMP
Hai guise,
I have spent many, many hours watching the GIMP re-scan all its plugins, scripts, brushes etc. every time it is started. At least a week, since I have been using the GIMP for a long time, with a lot of optional components installed. I think it would be a Good Thing if there was a way for users to tell the GIMP to load up a LOT faster.
I understand the usefulness of having the GIMP rebuild its library of components every time it is started: Add or remove a script, plugin or etc. and viola, the change takes effect when the GIMP is started, without further user intervention. That's the only sensible default behavior.
But I think it might also be very useful if there was a configuration option that would prompt the GIMP to save all this configuration data to a file the first time the program is started with the "fast open" option enabled, and load the configuration from that file on startup from then on. I imagine that would be a lot faster than building a new configuration from scratch at start time, every time.
That's just my imagination, of course. I would like to know what people who /really/ understand the GIMP start up process think about this. If saving and reloading configuration data would enable the GIMP to start "a lot" faster, an option for that would be popular with "a lot" of users.
When the user adds or removes components while a fast start mode is enabled, the GIMP could be prompted to rescan its directories via a configuration menu option. Alternately, the splash screen could have a dialog for that, i.e. buttons for "Start Now" and "Rescan Plugins."
So, what do y'all think? Would this actually work, and if so, would you want it?
:o)
Steve
Idea/Request: Fast start mode for GIMP
What version of GIMP are you using? I know from experience that a certain older version of GIMP did that every time it loaded however it was patched in later versions. If you have an older version, try the latest (2.8.16) and see if that fixes it.
- Kasim Ahmić
Sent from my iPhone
On Dec 17, 2015, at 2:26 PM, Steve Kinney wrote:
Hai guise,
I have spent many, many hours watching the GIMP re-scan all its plugins, scripts, brushes etc. every time it is started. At least a week, since I have been using the GIMP for a long time, with a lot of optional components installed. I think it would be a Good Thing if there was a way for users to tell the GIMP to load up a LOT faster.
I understand the usefulness of having the GIMP rebuild its library of components every time it is started: Add or remove a script, plugin or etc. and viola, the change takes effect when the GIMP is started, without further user intervention. That's the only sensible default behavior.
But I think it might also be very useful if there was a configuration option that would prompt the GIMP to save all this configuration data to a file the first time the program is started with the "fast open" option enabled, and load the configuration from that file on startup from then on. I imagine that would be a lot faster than building a new configuration from scratch at start time, every time.
That's just my imagination, of course. I would like to know what people who /really/ understand the GIMP start up process think about this. If saving and reloading configuration data would enable the GIMP to start "a lot" faster, an option for that would be popular with "a lot" of users.
When the user adds or removes components while a fast start mode is enabled, the GIMP could be prompted to rescan its directories via a configuration menu option. Alternately, the splash screen could have a dialog for that, i.e. buttons for "Start Now" and "Rescan Plugins."
So, what do y'all think? Would this actually work, and if so, would you want it?
:o)
Steve
_______________________________________________ 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
Idea/Request: Fast start mode for GIMP
On 12/17/2015 03:13 PM, Kasim Ahmic wrote:
What version of GIMP are you using? I know from experience that a certain older version of GIMP did that every time it loaded however it was patched in later versions. If you have an older version, try the latest (2.8.16) and see if that fixes it.
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. The more optional components you have, the longer it takes the GIMP to start. I do have a lot of brushes and more than the usual number of scripts and plugins...
:o)
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?
Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Idea/Request: Fast start mode for GIMP
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?
Using a 2.7GHz AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ the startup time is less than 3 seconds with 2.8.10 (Linux Mint 17.1)
Git edff1d0 also started in about 3 seconds on the second start. Wasn't counting for the first start, but sure it was more than 3 secs.
Fast enough for me !!
Owen
Idea/Request: Fast start mode for GIMP
On 12/17/2015 08:30 PM, Owen Cook 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?
Using a 2.7GHz AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ the startup time is less than 3 seconds with 2.8.10 (Linux Mint 17.1)
Git edff1d0 also started in about 3 seconds on the second start. Wasn't counting for the first start, but sure it was more than 3 secs.
Fast enough for me !!
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
Also present: GMIC, resynthesizer, wavelet decompose, animation support, a bunch of texture tiles and probably one or two other dealie bobs.
This isn't just clutter: All this junk is present because I have used it, at one time or another. I do a /lot/ of graphics work in several different contexts.
All of it needs found, identified, and menus configured to include it, every time the GIMP opens. Being able to save that state and just reload it in one go /should/, I believe, get the start up time down to "plenty fast enough."
The alternative would be removing most of that stuff, then adding back what is needed on a per-job basis, typically in mid course of editing an image. On the whole, I'll take the 40+ second opening time rather than that.
:o)
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
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 pluginYou 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
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
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 pluginYou 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)
Idea/Request: Fast start mode for GIMP
Elle Stone (ellestone@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
simon@budig.de http://simon.budig.de/
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
Idea/Request: Fast start mode for GIMP
On 12/18/2015 02:40 PM, Simon Budig wrote:
Elle Stone (ellestone@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'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-scale-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-shear-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-perspective-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-flip-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-cage-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-text-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-bucket-fill-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-blend-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-pencil-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-paintbrush-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-eraser-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-airbrush-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-ink-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-clone-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-heal-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-perspective-clone-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-convolve-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-smudge-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-dodge-burn-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-desaturate-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-color-balance-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-hue-saturation-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-colorize-tool'
Parsing
'/home/yeti/.gimp-2.8/tool-options/gimp-brightness-contrast-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-threshold-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-levels-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-curves-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-posterize-tool'
Parsing '/home/yeti/.gimp-2.8/tool-options/gimp-gegl-tool'
INIT: gimp_real_restore
Parsing '/home/yeti/.gimp-2.8/pluginrc'
Starting extension: 'extension-script-fu'
INIT: gui_restore_after_callback
Parsing '/home/yeti/.gimp-2.8/menurc'
Parsing '/home/yeti/.gimp-2.8/devicerc'
Parsing '/home/yeti/.gimp-2.8/controllerrc'
Parsing '/home/yeti/.gimp-2.8/colorrc'
loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for
/image-menubar
Loading module '/usr/lib/gimp/2.0/modules/libdisplay-filter-lcms.so'
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)
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
Idea/Request: Fast start mode for GIMP
[Sorry, should have gone to the list as well]
Steve Kinney (admin@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
simon@budig.de http://simon.budig.de/
- postings
- 1
Idea/Request: Fast start mode for GIMP
FYI,
i just installed gimp v 2.8.16 64bit on a Dell e6520, i5, 4G RAM, SSD and the startup time is invaryingly, that means always, 3 minutes 20 seconds.Of this 3 minutes belong to querying plugins.
Dominik
Idea/Request: Fast start mode for GIMP
On 03/31/2016 12:44 PM, dlen wrote:
FYI,
i just installed gimp v 2.8.16 64bit on a Dell e6520, i5, 4G RAM, SSD and the startup time is invaryingly, that means always, 3 minutes 20 seconds.Of this 3 minutes belong to querying plugins.
Lucky me: I just clocked GIMP opening time at 45 seconds with:
GIMP 2.8.10, every plugin set in the Debian/Ubuntu repos and a /lot/ of brushes and fonts, on a system with a 64 bit AMD dual core CPU, 1.75 GB memory and the Mint 17 OS.
An option to save and reload the data that the GIMP rebuilds every time it opens would be more helpful to some than others. With loading times up to 3 minutes 20 seconds, it could be called "make or break."
Idea/Request: Fast start mode for GIMP
Before the devs chime in... Normally Gimp will not re-register plug-ins (and so not execute them) if the file timestamp of the executable file has not changed since the previous registration). So on Linux Gimp startup times are good. But this seems to be broken on Windows.
On 01/04/16 00:11, Steve Kinney wrote:
On 03/31/2016 12:44 PM, dlen wrote:
FYI,
i just installed gimp v 2.8.16 64bit on a Dell e6520, i5, 4G RAM, SSD and the startup time is invaryingly, that means always, 3 minutes 20 seconds.Of this 3 minutes belong to querying plugins.
Lucky me: I just clocked GIMP opening time at 45 seconds with:
GIMP 2.8.10, every plugin set in the Debian/Ubuntu repos and a /lot/ of brushes and fonts, on a system with a 64 bit AMD dual core CPU, 1.75 GB memory and the Mint 17 OS.
An option to save and reload the data that the GIMP rebuilds every time it opens would be more helpful to some than others. With loading times up to 3 minutes 20 seconds, it could be called "make or break."
_______________________________________________ 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
Idea/Request: Fast start mode for GIMP
Hi,
On 1.4.2016 at 1:26 AM Ofnuts wrote:
Before the devs chime in... Normally Gimp will not re-register plug-ins (and so not execute them) if the file timestamp of the executable file has not changed since the previous registration). So on Linux Gimp startup times are good. But this seems to be broken on Windows.Hi,
thank you guys for reporting this. It's indeed an issue. We have filed some bugs with at least one solution proposal: https://bugzilla.gnome.org/show_bug.cgi?id=330099 https://bugzilla.gnome.org/show_bug.cgi?id=721184
IMHO all possible solutions be checked. Perhaps we find more in this
thread.
I'm for using the keyword 'performance' for all performance related
issues in Bugzilla, so the related bugs could be fixed in one go.
My 2p for now.
Greetings
Sven
Idea/Request: Fast start mode for GIMP
On April 1, 2016 1:26:14 AM GMT+02:00, Ofnuts wrote:
Before the devs chime in... Normally Gimp will not re-register plug-ins (and so not execute them) if the file timestamp of the executable file has not changed since the previous registration). So on Linux Gimp startup times are good. But this seems to be broken on Windows.
There is a known delay when reading scripts, ever since Unicode support was added to Script-Fu, IIRC.
But to my knowledge there is nothing that would suggest broken pluginrc handling.
Note that we do know next to nothing about the current case yet.
Idea/Request: Fast start mode for GIMP
On Thu, 2016-03-31 at 18:11 -0400, Steve Kinney wrote:
On 03/31/2016 12:44 PM, dlen wrote:
FYI,
i just installed gimp v 2.8.16 64bit on a Dell e6520, i5, 4G RAM, SSD and the
startup time is invaryingly, that means always, 3 minutes 20 seconds.Of this 3
minutes belong to querying plugins.Lucky me: I just clocked GIMP opening time at 45 seconds with:
GIMP 2.8.10, every plugin set in the Debian/Ubuntu repos and a /lot/ of brushes and fonts, on a system with a 64 bit AMD dual core CPU, 1.75 GB memory and the Mint 17 OS.
It takes between 10 and 13 seconds for gimp to start here on my laptop. Intel i7 @ 1.73 GHz, 8G of RAM, SSD. Both gimp-2.8.16 and git mistress from a day or two ago. Mageia GNU/Linux "Cauldron" (Mageia 6 preview). Probably faster on my desktop but I'm away at a conference in Toronto :-) (#techforum / #ebookcraft)
I have 125 or so scripts, over 7,000 fonts, but only a dozen or so plug-ins, 12MBytes of brushes.
If it's taking 45 seconds or more on comporable or faster hardware it might be something is wrong.
Does the "free" command say you're using swap space? (I actually am here, as firefox + evolution + gnome-shell together use more memory than I have installed).
Another possibility is that scanning fonts can take a long time if writing out the fontconfig cache fails. Running fc-cache -s as root may help.
I know there have been reported bugs about scanning all plug-ins on startup on Windows; in addition, some plugins (e.g. xsane) can do a lot of work when they're loaded. You can also get cache problems if your login directory is on a networked file system with an incorrect date, or if your system has an incorrect date.
Liam
Liam R. E. Quin
Idea/Request: Fast start mode for GIMP
Hi,
I took the time now and the chance to update our performance related bugs. There is already a keyword: perf. The performance related bugs (including the reported behaviour in this thread) are now found in the updated tracking bug https://bugzilla.gnome.org/show_bug.cgi?id=141797
Greetings
Sven
Idea/Request: Fast start mode for GIMP
On 04/01/2016 12:16 PM, Liam R. E. Quin wrote:
On Thu, 2016-03-31 at 18:11 -0400, Steve Kinney wrote:
On 03/31/2016 12:44 PM, dlen wrote:
FYI,
i just installed gimp v 2.8.16 64bit on a Dell e6520, i5, 4G RAM, SSD and the
startup time is invaryingly, that means always, 3 minutes 20 seconds.Of this 3
minutes belong to querying plugins.Lucky me: I just clocked GIMP opening time at 45 seconds with:
GIMP 2.8.10, every plugin set in the Debian/Ubuntu repos and a /lot/ of brushes and fonts, on a system with a 64 bit AMD dual core CPU, 1.75 GB memory and the Mint 17 OS.
It takes between 10 and 13 seconds for gimp to start here on my laptop. Intel i7 @ 1.73 GHz, 8G of RAM, SSD. Both gimp-2.8.16 and git mistress from a day or two ago. Mageia GNU/Linux "Cauldron" (Mageia 6 preview). Probably faster on my desktop but I'm away at a conference in Toronto :-) (#techforum / #ebookcraft)
I have 125 or so scripts, over 7,000 fonts, but only a dozen or so plug-ins, 12MBytes of brushes.
If it's taking 45 seconds or more on comporable or faster hardware it might be something is wrong.
On my other system, presently down for maintenance (needs monitor) with comparable specs and Mint 17, the current version of the GIMP takes 45 seconds to one minute to open.
On a previous system, one core CPU, 3/4 GB memory and Mint 14, the GIMP took 45 seconds to one minute to open.
On a one core Intel system with 1/2 GB memory and Windows XP SP3 (at a previous employer's office), GIMP 1.6 took 45 seconds to one minute to open.
On the ancient XP infested machine, I also ran into a problem where it took several minutes for the GIMP to open. I don't recall the details except that it was a font cache problem, easily fixed once diagnosed, restoring the 45 second to 1 minute loading time.
So either the slow loading GIMP experience is a fairly common thing, or I am an amazing statistical outlier.
:o)
Idea/Request: Fast start mode for GIMP
* Steve Kinney [04-01-16 16:26]: [...]
So either the slow loading GIMP experience is a fairly common thing, or I am an amazing statistical outlier.
on my openSUSE Tumbleweed, the first instance of gimp after entering graphical target is < 3 seconds, second and later instances < 2 seconds on my 4 year old i7.
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net
