Skip site navigation (1) Skip section navigation (2)

Re: concurrent IO in postgres?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "John W Strange" <john(dot)w(dot)strange(at)jpmchase(dot)com>, "wozniak(at)lanl(dot)gov" <wozniak(at)lanl(dot)gov>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: concurrent IO in postgres?
Date: 2010-12-23 19:02:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
John W Strange <john(dot)w(dot)strange(at)jpmchase(dot)com> 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?

In response to

pgsql-performance by date

Next:From: Przemek WozniakDate: 2010-12-23 19:46:57
Subject: Re: concurrent IO in postgres?
Previous:From: John W StrangeDate: 2010-12-23 18:47:58
Subject: Re: concurrent IO in postgres?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group