From: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | The right SHMMAX and FILE_MAX |
Date: | 2011-05-01 06:48:42 |
Message-ID: | BANLkTinCr_+Hs_zzHPb+tBdtuLFhrsfKdg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi. I'm on a 64 Bit CentOS 5 system, quadcore processor, 8GB RAM and
tons of data storage (1 TB SATAII disks).
The current SHMMAX and SHMMIN are (commas added for legibility) --
kernel.shmmax = 68,719,476,736
kernel.shmall = 4,294,967,296
Now, according to my reading in the PG manual and this list, a good
recommended value for SHMMAX is
(shared_buffers * 8192)
My postgresql.conf settings at the moment are:
max_connections = 300
shared_buffers = 300MB
effective_cache_size = 2000MB
By this calculation, shared_b * 8192 will be:
2,457,600,000,000
That's a humongous number. So either the principle for SHMMAX is
amiss, or I am reading this wrongly?
Similarly with "fs.file_max". There are articles like this one:
http://tldp.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap6sec72.html
Is this relevant for PostgreSQL performance at all, or should I skip that?
Thanks for any pointers!
From | Date | Subject | |
---|---|---|---|
Next Message | Mark | 2011-05-01 10:23:52 | Query improvement |
Previous Message | Samuel Gendler | 2011-05-01 01:00:34 | Re: stored proc and inserting hundreds of thousands of rows |