| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "jayknowsunix(at)gmail(dot)com" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Problems with PG 9.3 |
| Date: | 2014-08-26 20:26:09 |
| Message-ID: | CAOR=d=31qkmYbb-FTpOgGbMx=nDiPOxc3Os27uXxK7qWPnmf1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Aug 26, 2014 at 1:44 PM, Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> wrote:
> Here are all the changes
>
> max_connections =1000 -> 200
> work_mem =4GB -> 1GB
> temp_mem =2GB -> 1GB
> shared_buffers =80GB -> 70GB
> maintenance_work_mem = 16GB -> 2GB
> effective_cache_size =130GB -> 180GB
> max_locks_per_transaction =64 -> 128
> autovacuum_max_workers = 3 -> 12
> checkpoint_segments = 64 -> 256
OK, so while this is happening, what's you memory look like on the db
box? Is it running low on memory? Or does it have plenty left over for
kernel cache? Is it releasing a lot of kernel cache to make room for
work_mem? You need to profile your server while this is happening.
vmstat
iostat
htop
are good tools to start with.
Are you running out of memory, CPU, or IO?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2014-08-26 21:24:23 | Re: pg_basebackup man-page confusion? |
| Previous Message | Dhruv Shukla | 2014-08-26 19:44:11 | Re: Problems with PG 9.3 |