gpg: failed to create temporary file '/var/lib/lurker/.#lk0x571a0100.hantslug.org.uk.32592': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Tue Jul 13 19:30:04 2010 BST
gpg: using DSA key 2FF22CF403F94B5D
gpg: Can't check signature: No public key
On Tue, 2010-07-13 at 19:01 +0100, Hugo Mills wrote:
> Not that I'm aware of. Linux uses all the spare RAM for cache,
> because having spare RAM unused would be a waste. If a process
> actually needs more RAM (because it's starting up and allocating
> memory, say), then some files are evicted from cache to make space.
It uses it *very* aggressively, though, and seemingly with no way to
restrain it. To the point where copying a few large (order gigabytes)
files will cause the cache to grow to over 3/4 physical, and push out a
lot of stuff allocated to applications I'm using (including X). And then
interactivity just plummets. (I seem to remember a certain scientific
app that uses large amounts of RAM getting swapped out, too.)
Maybe there's some better setting for the writeback timeouts I could
try.
> There's a "swappiness" control that governs how much working set
> (i.e. the memory actually used by applications and not otherwise on
> disk) is swapped out to the pagefile, and how aggressively, but that
> won't help you with the filesystem cache bits.
I remember trying to tune swappiness down hard in the recent past and
arrived at the conclusion that the knob did pretty much nothing.
Certainly did not reduce Linux's tendency to swap out memory allocated
by processes in favour of the cache.
James
--
James TheHolyettlz@???
PGP key ID: 03F94B5D
-----------------------------------------------------------------------
