pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedSolaris Performance (Again)
5+ messages / 3 participants
[nested] [flat]
* Solaris Performance (Again)
@ 2003-12-10 05:56 Mark Kirkwood <markir@paradise.net.nz>
0 siblings, 2 replies; 5+ messages in thread
From: Mark Kirkwood @ 2003-12-10 05:56 UTC (permalink / raw)
To: pgsql-performance
This is a well-worn thread title - apologies, but these results seemed
interesting, and hopefully useful in the quest to get better performance
on Solaris:
I was curious to see if the rather uninspiring pgbench performance
obtained from a Sun 280R (see General: ATA Disks and RAID controllers
for database servers) could be improved if more time was spent
tuning.
With the help of a fellow workmate who is a bit of a Solaris guy, we
decided to have a go.
The major performance killer appeared to be mounting the filesystem with
the logging option. The next most significant seemed to be the choice of
sync_method for Pg - the default (open_datasync), which we initially
thought should be the best - appears noticeably slower than fdatasync.
We also tried changing some of the tuneable filesystem options using
tunefs - without any measurable effect.
Are Pg/Solaris folks running with logging on and sync_method default out
there ? - or have most of you been through this already ?
Pgbench Results (no. clients and transactions/s ) :
Setup 1: filesystem mounted with logging
No. tps
-----------
1 17
2 17
4 22
8 22
16 28
32 32
64 37
Setup 2: filesystem mounted without logging
No. tps
-----------
1 48
2 55
4 57
8 62
16 65
32 82
64 95
Setup 3 : filesystem mounted without logging, Pg sync_method = fdatasync
No. tps
-----------
1 89
2 94
4 95
8 93
16 99
32 115
64 122
Note : The Pgbench runs were conducted using -s 10 and -t 1000 -c 1->64,
2 - 3 runs of each setup were performed (averaged figures shown).
Mark
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Solaris Performance (Again)
@ 2003-12-10 13:53 Jeff <threshar@torgo.978.org>
parent: Mark Kirkwood <markir@paradise.net.nz>
1 sibling, 1 reply; 5+ messages in thread
From: Jeff @ 2003-12-10 13:53 UTC (permalink / raw)
To: Mark Kirkwood <markir@paradise.net.nz>; +Cc: pgsql-performance
On Wed, 10 Dec 2003 18:56:38 +1300
Mark Kirkwood <markir@paradise.net.nz> wrote:
> The major performance killer appeared to be mounting the filesystem
> with the logging option. The next most significant seemed to be the
> choice of sync_method for Pg - the default (open_datasync), which we
> initially thought should be the best - appears noticeably slower than
> fdatasync.
>
Some interesting stuff, I'll have to play with it. Currently I'm pleased
with my solaris performance.
What version of PG?
If it is before 7.4 PG compiles with _NO_ optimization by default and
was a huge part of the slowness of PG on solaris.
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Solaris Performance (Again)
@ 2003-12-10 19:15 Neil Conway <neilc@samurai.com>
parent: Mark Kirkwood <markir@paradise.net.nz>
1 sibling, 1 reply; 5+ messages in thread
From: Neil Conway @ 2003-12-10 19:15 UTC (permalink / raw)
To: Mark Kirkwood <markir@paradise.net.nz>; +Cc: pgsql-performance
Mark Kirkwood <markir@paradise.net.nz> writes:
> Note : The Pgbench runs were conducted using -s 10 and -t 1000 -c
> 1->64, 2 - 3 runs of each setup were performed (averaged figures
> shown).
FYI, the pgbench docs state:
NOTE: scaling factor should be at least as large as the largest
number of clients you intend to test; else you'll mostly be
measuring update contention.
-Neil
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Solaris Performance (Again)
@ 2003-12-11 06:04 Mark Kirkwood <markir@paradise.net.nz>
parent: Jeff <threshar@torgo.978.org>
0 siblings, 0 replies; 5+ messages in thread
From: Mark Kirkwood @ 2003-12-11 06:04 UTC (permalink / raw)
To: Jeff <threshar@torgo.978.org>; +Cc: pgsql-performance
Good point -
It is Pg 7.4beta1 , compiled with
CFLAGS += -O2 -funroll-loops -fexpensive-optimizations
Jeff wrote:
>
>What version of PG?
>
>If it is before 7.4 PG compiles with _NO_ optimization by default and
>was a huge part of the slowness of PG on solaris.
>
>
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Solaris Performance (Again)
@ 2003-12-11 06:09 Mark Kirkwood <markir@paradise.net.nz>
parent: Neil Conway <neilc@samurai.com>
0 siblings, 0 replies; 5+ messages in thread
From: Mark Kirkwood @ 2003-12-11 06:09 UTC (permalink / raw)
To: Neil Conway <neilc@samurai.com>; +Cc: pgsql-performance
yes - originally I was going to stop at 8 clients, but once the bit was
between the teeth....If I get another box to myself I will try -s 50 or
100 and see what that shows up.
cheers
Mark
Neil Conway wrote:
> FYI, the pgbench docs state:
>
> NOTE: scaling factor should be at least as large as the largest
> number of clients you intend to test; else you'll mostly be
> measuring update contention.
>
>-Neil
>
>
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2003-12-11 06:09 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-12-10 05:56 Solaris Performance (Again) Mark Kirkwood <markir@paradise.net.nz>
2003-12-10 13:53 ` Jeff <threshar@torgo.978.org>
2003-12-11 06:04 ` Mark Kirkwood <markir@paradise.net.nz>
2003-12-10 19:15 ` Neil Conway <neilc@samurai.com>
2003-12-11 06:09 ` Mark Kirkwood <markir@paradise.net.nz>
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