On Tue, Jan 6, 2009 at 11:02 AM, Stefano Nichele <stefano.nichele@xxxxxxxxx> wrote: > BTW, why did you said I/O bound ? Which are the parameters that highlight > that ? Sorry for my ignorance.... In addition to the percentage of time spent in wait as Scott said, you can also see the number of processes which are blocked (b column on the left). Those are the processes which would like to run but are waiting for IO to complete. >From your earlier vmstat output, you can see that often quite a large number of processes were waiting on IO - 20-30 of them. This is confirmed by your load average. Since you only have 6 spindles, during those periods, request service latency was likely very high during those periods. Anyway, I would start with significantly increasing the amount of memory you have allocated to shared_buffers. 32MB is _way_ too low. For a dedicated PostgreSQL machine with 4GB RAM, 1GB going to be a lot closer to optimal, with the optimal setting probably somewhere between 500MB and 2GB. And please post the rest of the information that the others have asked for... -Dave -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
