Re: ext2 vs ext3 vs RAID5 (software) benchmark - Mailing list pgsql-hackers

From Neil Conway
Subject Re: ext2 vs ext3 vs RAID5 (software) benchmark
Date
Msg-id 1015378074.31794.389.camel@jiro
Whole thread Raw
In response to ext2 vs ext3 vs RAID5 (software) benchmark  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-hackers
On Tue, 2002-03-05 at 20:01, Manuel Sugawara wrote:
> Today I made some benchmarks using Tatsuo's scripts to test the
> performance of ext2 vs ext3 vs software RAID5. Attached is the gnuplot
> output. Note that the RAID5 setup has the WAL in another partition
> with RAID1 and both are spread across three SCSI disks. The machine is
> a dual pentium III 1 Ghz with 2Gb in RAM running RedHat 7.2 and
> PostgreSQL 7.2.

The poor performance of ext3 is interesting. You could try mounting ext3
with "data=writeback", as there is no benefit to preserving write
ordering with Postgres (because it has WAL, anyway). That should improve
performance slightly, but certainly not by a factor of 3.

In fact, I can reproduce these results locally (for ext2 & ext3): ext3
tops out at around 11 TPS, ext2 at 21 to 29 TPS, and ext3 with
data=writeback at 16 TPS (running pgbench, 100 transactions). I wasn't
aware that the speed penalty for ext3 was this high...

For the very simple benchmarks I was running, ext3's poor performance
might be explained by the more conservative buffering used by ext3
(flushing buffers to disk every 5 seconds, not every 30 seconds like
with ext2) -- but I'm sure that your benchmarks were running for a much
longer period of time, right? BTW, what are "Tatsuo's scripts", which
you said you were using?

It would be interesting to see the results using other filesystems, like
XFS or ReiserFS. If you can gather some more data, you could send this
off to the linux kernel list, they would probably be interested in ext3
performance under "real" load.

Cheers,

Neil

-- 
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC



pgsql-hackers by date:

Previous
From: "Rod Taylor"
Date:
Subject: Re: Intervening in Parser -> Planner Stage
Next
From: Justin Clift
Date:
Subject: Do we still have locking problems with concurrent users of hash tables?