From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: the Gimp and pre11
Date: Wed, 19 Sep 2001 12:30:18 -0700 [thread overview]
Message-ID: <20010919123018.B12820@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20010919034412.092EB9CF9@oscar.casa.dyndns.org> <1000907347.6897.8.camel@sonja>
In-Reply-To: <1000907347.6897.8.camel@sonja>
On Wed, Sep 19, 2001 at 03:48:57PM +0200, Daniel Egger wrote:
> On Mit, 2001-09-19 at 05:44, Ed Tomlinson wrote:
>
> > I am editing 6 Megapixel files (2800x2048) and things like rotations seem to
> > have delays that were not happening with previous kernels. My box has 320M.
> > Seems that pre11 does not swap out as much as pre10 so Gimp has less to work
> > with.
>
> Since GIMP uses it's own memory management using a tile approach I
> hardly doubt this is caused by swap usage if you defined the maximum
> amount of memory GIMP should use correctly; though it may be that the
> kernel swaps out tiles that the tilemanager considers to be active (and
> thus in memory) this behaviour should not happen as long as the kernel
> is not to eagerly swapping out memory and considering that the tiles
> are referenced quite often it should not swap them to disc at all IF
> the recently introduced algorithms work correctly.
>
> Anyhow, just to make sure, would you please mention much memory you
> assigned to GIMP and what else is running on the system?
>
Also, try a test with pre11 with swap turned off, and see how that affects
your system.
Please note: I am not recommending running without swap under normal
circumstances...
prev parent reply other threads:[~2001-09-19 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 3:44 the Gimp and pre11 Ed Tomlinson
2001-09-19 13:48 ` Daniel Egger
2001-09-19 19:30 ` Mike Fedyk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010919123018.B12820@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.