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
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 R. E. Quin <l...@holoweb.net>
gimp-user-list mailing list
List address: email@example.com
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives: https://mail.gnome.org/archives/gimp-user-list