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
-Dhruv
On Tue, Aug 26, 2014 at 2:37 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote:
On Tue, Aug 26, 2014 at 1:32 PM, Dhruv Shukla <dhruvshukla82@xxxxxxxxx> wrote:OK increasing max locks per transaction is pretty safe. What did you
> Scott,
> Thanks for such a valuable information. I will have a look into it and have
> it debugged.
>
> But now things have started slowing down really. Some programs have started
> to throw errors like
>
> ERROR: DB COPY failed: DBD::Pg::db pg_endcopy
> failed: ERROR: out of shared memory
> HINT: You might need to increase max_locks_per_transaction.
>
>
> These were things which were working before with higher memory settings. And
> some are just running slow, slow means literally slow even though they are
> connected via netstat and all.
change shared_mem from and too? Setting it a bit higher isn't terribly
dangerous, like work_mem x max_conns can be.
Regards
Dhruv
404-551-2578
