pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Finding bottleneck
Date: Fri, 19 Aug 2005 10:03:12 -0400
Message-ID: <17939.1124460192@sss.pgh.pa.us> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3417DD150@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD150@Herge.rcsinc.local>

"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> Relative to 8.0, I am seeing a dramatic, almost miraculous reduction in
> CPU load times in 8.1devel.  This is for ISAM style access patterns over
> the parse/bind interface.  (IOW one record at a time, 90% read, 10%
> write).

> Relative to commercial dedicated ISAM storage engines, pg holds up very
> well except in cpu load, but 8.1 is a huge step towards addressing that.

Cool --- we've done a fair amount of work on squeezing out internal
inefficiencies during this devel cycle, but it's always hard to predict
just how much anyone will notice in the real world.

Care to do some oprofile or gprof profiles to see where it's still bad?

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <17939.1124460192@sss.pgh.pa.us>
Permalink:  ../17939.1124460192@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17939.1124460192@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, merlin.moncure@rcsonline.com
  Subject: Re: Finding bottleneck
  In-Reply-To: <17939.1124460192@sss.pgh.pa.us>

* 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