> 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
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.
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
>
> 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
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
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
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
[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'
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
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,
10 matches
Mail list logo
