From: | Mark Wong <markw(at)osdl(dot)org> |
---|---|
To: | Rod Taylor <pg(at)rbt(dot)ca> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, testperf-general(at)pgfoundry(dot)org |
Subject: | Re: 8.0beta5 results w/ dbt2 |
Date: | 2004-11-30 16:55:01 |
Message-ID: | 20041130085501.F18011@osdl.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 30, 2004 at 11:03:03AM -0500, Rod Taylor wrote:
> On Mon, 2004-11-29 at 16:01 -0800, Mark Wong wrote:
> > I have some initial results using 8.0beta5 with our OLTP workload.
> > Off the bat I see about a 23% improvement in overall throughput. The
> > most significant thing I've noticed was in the oprofile report where
> > FunctionCall2 and hash_seq_search have moved down the profile a bit.
> >
> > Also, I have libc with symbols now so we can see what it's doing with
> > in the oprofile output.
> >
> > 8.0beta5 results:
> > http://www.osdl.org/projects/dbt2dev/results/dev4-010/199/
> > throughput: 4076.97
> >
> > 8.0beta4 results:
> > http://www.osdl.org/projects/dbt2dev/results/dev4-010/191/
> > throughput: 3323.07
>
> It appears that WAL archiving (archive_command) is configured in 191 and
> disabled (unset) in 199. Perhaps this accounts for some of the
> difference?
>
I've found the archiving to be about a 1% overhead and in all my
random testing since then I haven't seen evidence otherwise. Here's
a linke to that message:
http://archives.postgresql.org/pgsql-hackers/2004-09/msg00430.php
But I'll try again too as things may have changed.
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-11-30 16:55:32 | Re: VACUUM FULL FREEZE is unsafe |
Previous Message | Andrew Dunstan | 2004-11-30 16:45:56 | Re: Error handling in plperl and pltcl |