| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Charles Nadeau <charles(dot)nadeau(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Very poor read performance, query independent |
| Date: | 2017-07-12 13:57:06 |
| Message-ID: | DM5PR07MB281020250424625EAAFDD77ADAAF0@DM5PR07MB2810.namprd07.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
From: Charles Nadeau [mailto:charles(dot)nadeau(at)gmail(dot)com]
Sent: Wednesday, July 12, 2017 3:21 AM
To: Igor Neyman <ineyman(at)perceptron(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Very poor read performance, query independent
Igor,
I set shared_buffers to 24 GB and effective_cache_size to 64GB and I can see that the queries are faster due to the fact that the index are used more often. Knowing I have 72GB of RAM and the server is exclusively dedicated to Postgresql, what could be the maximum value for effective_cache?
Thanks!
Charles
64GB for effective_cache_size should be good enough, adding couple more GB wouldn’t change much.
Igor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Otten | 2017-07-12 14:10:27 | Re: Very poor read performance, query independent |
| Previous Message | Charles Nadeau | 2017-07-12 13:38:23 | Re: Very poor read performance, query independent |