pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anjan Dave <adave@vantage.com>
Cc: Matt Clark <matt@ymogen.net>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: can't handle large number of INSERT/UPDATEs
Date: Tue, 26 Oct 2004 18:37:32 -0400
Message-ID: <14215.1098830252@sss.pgh.pa.us> (raw)
In-Reply-To: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DE@vt-pe2550-001.vantage.vantage.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF7850985DE@vt-pe2550-001.vantage.vantage.com>

"Anjan Dave" <adave@vantage.com> writes:
> One thing I am not sure is why 'bi' (disk writes) stays at 0 mostly,
> it's the 'bo' column that shows high numbers (reads from disk). With so
> many INSERT/UPDATEs, I would expect it the other way around...

Er ... it *is* the other way around.  bi is blocks in (to the CPU),
bo is blocks out (from the CPU).

			regards, tom lane



view thread (24+ messages)  latest in thread

Message-ID: <14215.1098830252@sss.pgh.pa.us>
Permalink:  ../14215.1098830252@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14215.1098830252@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, adave@vantage.com, matt@ymogen.net, pg@rbt.ca
  Subject: Re: can't handle large number of INSERT/UPDATEs
  In-Reply-To: <14215.1098830252@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