John W Strange <john.w.strange@xxxxxxxxxxxx> wrote: > Typically my problem is that the large queries are simply CPU > bound. Well, if your bottleneck is CPU, then you're obviously not going to be driving another resource (like disk) to its limit. First, though, I want to confirm that your "CPU bound" case isn't in the "I/O Wait" category of CPU time. What does `vmstat 1` show while you're CPU bound? If it's not I/O Wait time, then you need to try to look at the queries involved. If you're not hitting the disk because most of the active data is cached, that would normally be a good thing. What kind of throughput are you seeing? Do you need better? http://wiki.postgresql.org/wiki/SlowQueryQuestions -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
