pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Kavan, Dan (IMS) <KavanD@imsweb.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: benchmarks with pgbench
Date: Mon, 24 Jan 2005 11:12:22 -0600
Message-ID: <1106586742.16640.94.camel@state.g2switchworks.com> (raw)
In-Reply-To: <782D2A81EC812642B857B03B506E0B44309A05@granite.omni.imsweb.com>
References: <782D2A81EC812642B857B03B506E0B44309A05@granite.omni.imsweb.com>

On Mon, 2005-01-24 at 10:48, Kavan, Dan (IMS) wrote:
>       Hi Guys,
> I''ve been running pgbench tests for a while.  I have one server set up
> to run pgbench tpc tests (7.x).  A new server that I just configured
> with SUSE and 8.0.0 just gets killed even though it has the same memory
> 8 GB and it's a x86-64 box.  The other one is Solaris full 64-bit.  That
> seems reasonable, but we thought postgres would run better on a linux
> box than solaris.  Also, the x86-64 box does much worse than  a 32-bit
> linux box with mandrake and a lot less RAM.  I've restarted postgres
> with many different postgresql.conf configs and nothing seems to make
> much of a difference to pgbench.  Has anyone else experienced slower
> performance on 64-bit linux as compared to 32-bit linux?

pgbench is notorious for providing poor measure of a database's
performance under real world load.  Are you sure your Solaris and Linux
boxes are both running on SCSI hard drives (IDE drives are well known
for not obeying fsync() calls, but simply saying "yep, synced that data"
when in fact they haven't.  So, if you Linux box is set to both fsync
properly AND is writing access time to each file, it may be quite a bit
slower than a Solaris box if that box is writing to IDE drives, has
fsync turned off, and / or has access time writing disabled.



view thread (5+ messages)  latest in thread

Message-ID: <1106586742.16640.94.camel@state.g2switchworks.com>
Permalink:  ../1106586742.16640.94.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1106586742.16640.94.camel@state.g2switchworks.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 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-admin@postgresql.org
  Cc: smarlowe@g2switchworks.com, KavanD@imsweb.com
  Subject: Re: benchmarks with pgbench
  In-Reply-To: <1106586742.16640.94.camel@state.g2switchworks.com>
  References: <782D2A81EC812642B857B03B506E0B44309A05@granite.omni.imsweb.com> <1106586742.16640.94.camel@state.g2switchworks.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