pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: captainx0r@yahoo.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Sun vs. Mac
Date: Tue, 14 Jan 2003 11:04:52 -0500
Message-ID: <16237.1042560292@sss.pgh.pa.us> (raw)
In-Reply-To: <20030114154121.53714.qmail@web21103.mail.yahoo.com>
References: <20030114154121.53714.qmail@web21103.mail.yahoo.com>

CaptainX0r <captainx0r@yahoo.com> writes:
> I've read that somewhere (maybe in the archives?) and I got no
> change with any of them.  But now I'm thinking back - do I need
> fsync=true for that to have an affect?  I'm not worried about
> the cons of having fsync=false at all - and I'm assuming that
> should be better than true and open_datasync. 

You are right that fsync_method is a no-op if you've got fsync turned
off.

Let me get this straight: the Sun is slower even with fsync off?  That
shoots down the first theory that I had, which was that the Sun's disk
drives were actually honoring fsync while the laptop's drive does not.
(See archives for more discussion of that, but briefly: IDE drives are
commonly set up to claim write complete as soon as they've absorbed
data into their onboard buffers.  SCSI drives usually tell the truth
about when they've completed a write.)

Andrew Sullivan's nearby recommendation to replace qsort() is a good
one, but PG 7.3 is already configured to do that by default.  (Look in
src/Makefile.global to confirm that qsort.o is mentioned in LIBOBJS.)

I'd suggest starting with some elementary measurements, for example
looking at I/O rates and CPU idle percentage while running the same
task on both Solaris and G3.  That would at least give us a clue whether
I/O or CPU is the bottleneck.

			regards, tom lane



view thread (20+ messages)  latest in thread

Message-ID: <16237.1042560292@sss.pgh.pa.us>
Permalink:  ../16237.1042560292@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16237.1042560292@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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, captainx0r@yahoo.com
  Subject: Re: Sun vs. Mac
  In-Reply-To: <16237.1042560292@sss.pgh.pa.us>
  References: <20030114154121.53714.qmail@web21103.mail.yahoo.com> <16237.1042560292@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