| Re: OpenVZ & PostgreSQL: shmpages, shared_buffers, kernel.shmmax [message #33811 is a reply to message #33801] |
Wed, 12 November 2008 07:19   |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Hi Collin,
1) you don't need to change /sbin/sysctl kernel.shmmax in the host node as those setting would not affect Container's settings.
2) if you really want to run just a single Container on a Node, you can just disable memory limitation for the Container - just set "shmpages" and "privvmpages" UBC to any _big_ number, greater than 8Gb.
And you can also set /sbin/sysctl kernel.shmmax in the Container to the 8Gb (so you'll never reach this limit).
3) i cannot tell you anything useful about shared_buffers in PostgreSQL - know nothing about it. i've googled a bit and seen that people mostly use from 128Mb to 1Gb but suggest to increase this value in case of memory PostreSQL allocation failures.
Don't know if it's useful for PostreSQL, but you may increase those parameters - i only guess! - up to 6-7Gb if you don't run anything else on the Node (i think it makes sense to leave some memory for system itself).
But i'd advise to play with that parameter - it might be optimal for the whole system not to provide ALL the memory to PostgreSQL.
BTW, it will be very useful if you post here values you chosen after your experiments.
Hope this helps.
--
Konstantin
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
