Re: Fwd: [PERFORM] Problems with pg_locks explosion

2013-04-01 Thread Mark Kirkwood
Yeah, as I understand it you should have 6000 IOPS available for the md device (ideally). The iostats you display certainly look benign... but the key time to be sampling would be when you see the lock list explode - could look very different then. Re vm.dirty* - I would crank the values dow

Fwd: [PERFORM] Problems with pg_locks explosion

2013-04-01 Thread Armand du Plessis
Thanks Mark, I had a look at the iostat output (on a 5s interval) and pasted it below. The utilization and waits seems low. Included a sample below, #1 taken during normal operation and then when the locks happen it basically drops to 0 across the board. My (mis)understanding of the IOPS was that

Fwd: [PERFORM] Problems with pg_locks explosion

2013-04-01 Thread Vasilis Ventirozos
Hello, i think that your system during the checkpoint pauses all clients in order to flush all data from controller's cache to the disks if i were you i'd try to tune my checkpoint parameters better, if that doesn't work, show us some vmstat output please Vasilis Ventirozos -- Forwarded me