pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Alan Stange <stange@rentec.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Excessive context switching on SMP Xeons
Date: 06 Oct 2004 03:44:02 -0400
Message-ID: <87acv0z3y5.fsf@stark.xeocode.com> (raw)
In-Reply-To: <41636D8E.1090403@rentec.com>
References: <4162CA14.6080206@lulu.com>
	<200410050947.36174.josh@agliodbs.com>
	<41630D50.3020308@lulu.com>
	<200410051538.51664.josh@agliodbs.com>
	<41636D8E.1090403@rentec.com>


Alan Stange <stange@rentec.com> writes:

> A few quick random observations on the Xeon v. Opteron comparison:
> 
> - running a dual Xeon with hyperthreading turned on really isn't the same as
> having a quad cpu system. I haven't seen postgresql specific benchmarks, but
> the general case has been that HT is a benefit in a few particular work
> loads but with no benefit in general.

Part of the FUD with hyperthreading did have a kernel of truth that lied in
older kernels' schedulers. For example with Linux until recently the kernel
can easily end up scheduling two processes on the two virtual processors of
one single physical processor, leaving the other physical processor totally
idle.

With modern kernels' schedulers I would expect hyperthreading to live up to
its billing of adding 10% to 20% performance. Ie., a dual Xeon machine with
hyperthreading won't be as fast as four processors, but it should be 10-20%
faster than a dual Xeon without hyperthreading.

As with all things that will only help if you're bound by the right limited
resource to begin with. If you're I/O bound it isn't going to help. I would
expect Postgres with its heavy demand on memory bandwidth and shared memory
could potentially benefit more than usual from being able to context switch
during pipeline stalls.

-- 
greg




view thread (17+ messages)  latest in thread

Message-ID: <87acv0z3y5.fsf@stark.xeocode.com>
Permalink:  ../87acv0z3y5.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87acv0z3y5.fsf@stark.xeocode.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gsstark@mit.edu, stange@rentec.com, josh@agliodbs.com
  Subject: Re: Excessive context switching on SMP Xeons
  In-Reply-To: <87acv0z3y5.fsf@stark.xeocode.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox