Re: [HACKERS] high shared buffer and swap

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: Laurent Laborde <kerdezixe(at)gmail(dot)com>
Cc: PFC <lists(at)peufeu(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: [HACKERS] high shared buffer and swap
Date: 2009-05-05 11:24:42
Message-ID: alpine.DEB.2.00.0905051220050.2341@aragorn.flymine.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Tue, 5 May 2009, Laurent Laborde wrote:
> I tried with swappinness set to 0 and ... it swaps !

While I wouldn't presume to try and teach you to suck eggs, once you set
swappiness to zero the system will take a while to settle down. The
swappiness setting will stop it swapping out, but if there is stuff out in
swap, then it won't force it to swap it in early. So the machine will
still thrash when it tries to access something that is out on swap. Easy
way to solve this is to swapoff the various swap partitions, which will
force it all into memory. You can swapon them again afterwards.

Matthew

--
Surely the value of C++ is zero, but C's value is now 1?
-- map36, commenting on the "No, C++ isn't equal to D. 'C' is undeclared
[...] C++ should really be called 1" response to "C++ -- shouldn't it
be called D?"

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mito 2009-05-05 11:46:07 Values of fields in Rules
Previous Message Bernd Helmle 2009-05-05 10:39:23 bytea vs. pg_dump

Browse pgsql-performance by date

  From Date Subject
Next Message Bryan Murphy 2009-05-06 00:54:00 Re: Limit I/O bandwidth of a certain backend
Previous Message Laurent Laborde 2009-05-05 10:20:01 Re: [HACKERS] high shared buffer and swap