pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marc Cousin <cousinmarc@free.fr>
To: pgsql-performance@postgresql.org
Subject: Re: Optimicing Postgres for SunSolaris10 on V240
Date: Sat, 18 Nov 2006 10:08:44 +0100
Message-ID: <200611181008.44972.cousinmarc@free.fr> (raw)
In-Reply-To: <455E02FC.6020103@agliodbs.com>
References: <20061117155255921.00000002448@sbzvzgws084>
	<455E02FC.6020103@agliodbs.com>

Hi...

Bacula does no transaction right now, so every insert is done separately with 
autocommit.
Moreover, the insert loop for the main table is done by several individual
queries to insert data in several tables (filename, dir, then file), so this
is slow.
There's work underway to speed that up, using a big COPY to a temp table,
then queries to dispatch the records in the right places as fast as
possible. The patch has been made, but as it is a noticeable change in the
core, will take some time to be integrated... See the thread about that in
the bacula devel list a few weeks ago... Anyhow, our benchmark for now shows
a 10-20 times speedup with postgresql, fsync stays on, and it becomes faster
than mysql, and scales with the number of cpus... I cannot tell when/if it
will be included, but there's work on this.

For now, the only thing you can do is fsync=off, knowing you're taking a
chance with the data (but it's not that big a problem, as it's only bacula's
database, and can be rebuilt from the tapes or from a dump...) or a writeback
disk controller.



On Friday 17 November 2006 19:44, Josh Berkus wrote:
> Berner,
>
> First, I've corrected you e-mail so that it goes to the list, and not to
> me directly.
>
> > I use my PostgreSQL 8.0.4 as Catalogue-Database for Bacula.
> > Bacula is a Backupsoftware.
>
> Yes.  The lead contributor to Bacula is a active PostgreSQL project
> participant; I'll see if he'll look into your issue.
>
> > When I backing up System (lot of very small Files) then PostgreSQL seams
> > to by the bottleneck by inserting Catalogueinformation of every single
> > File. The System on which Postgres runs is a Sun Solaris 10 Server on a
> > Sun Fire V240 with 1GB RAM, 1CPU (SUNW,UltraSPARC-IIIi at 1.3GHz), 2
> > Ultra SCSI-3 Disks 73GB at 10k RPM which are in Raid1 (Solaris Softraid).
> >
> > Can someone gif me a hint for compiling PostgreSQL or configuring the
> > Database.
> >
> > fsync is already disabled..
>
> This is a bad idea if you care about your database.
>
> So, PostgreSQL 8.1 is now official supported by Sun and ships with
> Solaris 10 update 2 or later.  It is recommended that you use that
> rather and an out-of-date version.   Second, see
> www.powerpostgresql.com/PerfList
>
> --Josh Berkus
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster



view thread (2+ messages)

Message-ID: <200611181008.44972.cousinmarc@free.fr>
Permalink:  ../200611181008.44972.cousinmarc@free.fr/
Also on:    postgresql.org/message-id/200611181008.44972.cousinmarc@free.fr

 · 

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: cousinmarc@free.fr
  Subject: Re: Optimicing Postgres for SunSolaris10 on V240
  In-Reply-To: <200611181008.44972.cousinmarc@free.fr>

* 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