On Tue, 5 May 2009, Vlad Arkhipov wrote:
Is there a way to limit I/O bandwidth/CPU usage of a certain backend? It
seems that ionice/renice makes no sense because of bgwriter/WAL writer
processes are not a part of a backend.
The background writer and WAL writer are pretty low users of CPU and I
On Tue, May 5, 2009 at 2:31 AM, Vlad Arkhipov wrote:
> Is there a way to limit I/O bandwidth/CPU usage of a certain backend? It
> seems that ionice/renice makes no sense because of bgwriter/WAL writer
> processes are not a part of a backend. I have a periodic query (every
> hour) that make huge I/
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 the
On Tue, May 5, 2009 at 11:15 AM, PFC wrote:
>
>> An octocore server with 32GB of ram, running postgresql 8.3.6
>> Running only postgresql, slony-I and pgbouncer.
>>
>> Just for testing purpose, i tried a setting with 26GB of shared_buffer.
>>
>> I quickly noticed that the performances wasn't very
An octocore server with 32GB of ram, running postgresql 8.3.6
Running only postgresql, slony-I and pgbouncer.
Just for testing purpose, i tried a setting with 26GB of shared_buffer.
I quickly noticed that the performances wasn't very good and the
server started to swap slowly but surely.
(but
Is there a way to limit I/O bandwidth/CPU usage of a certain backend? It
seems that ionice/renice makes no sense because of bgwriter/WAL writer
processes are not a part of a backend. I have a periodic query (every
hour) that make huge I/O load and should run in background. When this
query runs all
