From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
---|---|
To: | Cosimo Streppone <cosimo(at)streppone(dot)it> |
Cc: | Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: postgresql-8.0.1 performance tuning |
Date: | 2005-06-01 07:22:42 |
Message-ID: | 429D6242.6000804@paradise.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Cosimo Streppone wrote:
> Mark Kirkwood ha scritto:
>
>> Cosimo Streppone wrote:
>>
>>> ######### Config ############
>>>
>>>> /etc/sysctl.conf:
>>>> kernel.shmall = 786432000
>>>> kernel.shmmax = 786432000
>>>
>>>
>>> I think you have a problem here.
>>> kernel.shmmax should *not* be set to an amount of RAM, but
>
>
> Sorry, I thought "shmall" but written "shmmax".
> Thanks Mark!
>
Hehe - happens to me all the time!
On the shmall front - altho there is *probably* no real performance
impact setting it to the same as shmmax (i.e. allowing 4096 allocations
of size shmmax!), it is overkill. In addition it does allow for a DOS by
a program that allocates thousands of segments (or somehow starts
thousands of Pg servers on different ports...)!
For a dedicated Pg server I would size shmall using a calculation along
the lines of:
shmall = (no. of postgresql servers) * (shmmax/4096)
If there are other daemons on the box that need to use shared memory,
then add their likely requirements to shmall too!
cheers
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Mindaugas Riauba | 2005-06-01 07:43:06 | How to avoid database bloat |
Previous Message | Cosimo Streppone | 2005-06-01 06:44:18 | Re: postgresql-8.0.1 performance tuning |