On Tue, Aug 26, 2014 at 1:44 PM, Dhruv Shukla <dhruvshukla82@xxxxxxxxx> 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? -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
