Message-ID: <454B3B75.6@archonet.com>
Date: Fri, 03 Nov 2006 12:52:05 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060918)
MIME-Version: 1.0
To: creimer@brturbo.com.br
Cc: pgsql-performance@postgresql.org
Subject: Re: Context switch storm
References: <efc1d7c07cf.454afe8d@brturbo.com.br>
In-Reply-To: <efc1d7c07cf.454afe8d@brturbo.com.br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

creimer@brturbo.com.br wrote:
> Hi,
> 
> We've migrated one of our servers from pg 7.4 to 8.1 and from times
> to times (4 hours) the server start doing a lot of context switching
> and all transactions become very slow.
> 
> The average context switching for this server as vmstat shows is 1
> but when the problem occurs it goes to 250000.
> 
> CPU and memory usage are ok.
> 
> What is producing this context switching storms?
 >
> It is a box with 16GB RAM and 4 XEON processors running RedHat
> Enterprise Linux AS.

It's memory bandwidth issues on the older Xeons. If you search the 
archives you'll see a lot of discussion of this. I'd have thought 8.1 
would be better than 7.4 though.

You'll tend to see it when you have multiple clients and most queries 
can use RAM rather than disk I/O. My understanding of what happens is 
that PG requests data from RAM - it's not in cache so the process gets 
suspended to wait. The next process does the same, with the same result. 
   You end up with lots of processes all fighting over what data is in 
the cache and no-one gets much work done.

> Should I disable Hyperthreading?

I seem to remember that helps, but do check the mailing list archives 
for discussion on this.

If you can keep your numbers of clients down below the critical level, 
you should find the overall workload is fine. The problem is of course 
that as the context-switching increases, each query takes longer which 
means more clients connect, which increases the context-swtching, which 
means...

HTH
-- 
   Richard Huxton
   Archonet Ltd