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 be
* 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
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
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
S
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
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
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,
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 sec
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
--
dlen (via www.gimpusers.com/forums)
___
gi
[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'
P
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 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
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 plugin
>
> 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 number
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
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 reaso
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 "installe
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
> 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
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?
>
>
> > 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 Pr
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,
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
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
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
25 matches
Mail list logo
