pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: alex@neteconomist.com
Cc: pgsql-performance@postgresql.org
Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
Date: 11 Jan 2005 10:39:01 -0500
Message-ID: <87zmzg0ycq.fsf@stark.xeocode.com> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A75A3@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A75A3@Herge.rcsinc.local>


"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:

> heh, our apps do tend to be CPU bound.  Generally, I think the extra CPU
> horsepower is worth the investment until you get to the really high end
> cpus.

I find that while most applications I work with shouldn't be cpu intensive
they do seem end up being cpu bound quite frequently. What happens is that 90%
of the workload has a working set that fits in RAM. So the system ends up
being bound by the memory bus speed. That appears exactly the same as
cpu-bound, though I'm unclear whether increasing the cpu clock will help.

It's quite possible to have this situation at the same time as other queries
are i/o bound. It's quite common to have 95% of your workload be frequently
executed fast queries on commonly accessed data and 5% be bigger data
warehouse style queries that need to do large sequential reads.

Incidentally, the same was true for Oracle on Solaris. If we found excessive
cpu use typically meant some frequently executed query was using a sequential
scan on a small table. Small enough to fit in RAM but large enough to consume
lots of cycles reading it.

-- 
greg




view thread (36+ messages)  latest in thread

Message-ID: <87zmzg0ycq.fsf@stark.xeocode.com>
Permalink:  ../87zmzg0ycq.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87zmzg0ycq.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, merlin.moncure@rcsonline.com, alex@neteconomist.com
  Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  In-Reply-To: <87zmzg0ycq.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