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


Alex Turner <armtuk@gmail.com> writes:

> Infact the cache hit ratio that Oracle suggests is the minimum good
> value is 95%.  Anything below that is bad news.  

Well that seems very workload dependent. No amount of cache is going to be
able to achieve that for a DSS system chugging sequentially through terabytes
of data. Whereas for OLTP systems I would wouldn't be surprised to see upwards
of 99% hit rate.

Note that a high cache hit rate can also be a sign of a problem. After all, it
means the same data is being accessed repeatedly which implicitly means
something is being done inefficiently. For an SQL database it could mean the
query plans are suboptimal.

On several occasions we found Oracle behaving poorly despite excellent cache
hit rates because it was doing a sequential scan of a moderately sized table
instead of an index lookup. The table was small enough to fit in RAM but large
enough to consume a significant amount of cpu, especially with the query being
run thousands of times per minute.

-- 
greg




view thread (36+ messages)  latest in thread

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