pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: shridhar_daithankar@persistent.co.in
To: pgsql-performance@postgresql.org
Subject: Re: Insert performance
Date: Sat, 16 Aug 2003 11:40:59 -0700
Message-ID: <200308161140.59764.josh@agliodbs.com> (raw)
In-Reply-To: <3F3E3B47.13828.333B51D9@localhost>
References: <3F3E3B47.13828.333B51D9@localhost>

Shridhar,

> Unfortunately he can not use copy due to some constraints. 

Why not use COPY to load the table, and then apply the constraints by query 
afterwords?  It might not be faster, but then again it might.

> I was really amazed to see the numbers. First of all, it beat the sunOS
> machine left and right. Bruce posted some numbers of 9K inserts/sec. Here
> we see the same.
<snip>
> Comments? One thing I can't help to notice is sunOs is not on same scale.
> The sunOS machine is a 1GB RAM machine. It has oracle and mysql running on
> it and have 300MB swap in use but I am sure it has SCSI disk and in all
> respect I would rather expect a RISC machine to perform better than an
> athlon XP machine, at least for an IO.

It's been reported on this list several times that Solaris is the *worst* of 
the *nixes for PostgreSQL performance.   No analysis has been posted as to 
why; my own thoughts are:
	- Solaris' multi-threaded architecture which imposes a hefty per-process 
overhead, about triple that of Linux, slowing new connections and large 
multi-user activity;
	- Poor filesystem management; Sun simply hasn't kept up with IBM, Reiser, Red 
Hat and BSD in developing filesystems.
	... but that's based on inadequate experimentation, just a few tests on 
Bonnie++ on a Netra running Solaris 8.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (32+ messages)  latest in thread

Message-ID: <200308161140.59764.josh@agliodbs.com>
Permalink:  ../200308161140.59764.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200308161140.59764.josh@agliodbs.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: josh@agliodbs.com, shridhar_daithankar@persistent.co.in
  Subject: Re: Insert performance
  In-Reply-To: <200308161140.59764.josh@agliodbs.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