From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: test_fsync open_sync test |
Date: | 2011-01-18 18:49:49 |
Message-ID: | 201101181849.p0IInnP13876@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Smith wrote:
> Bruce Momjian wrote:
> > Is there a value to this test_fsync test?
> >
> > Compare open_sync with different sizes:
> > (This is designed to compare the cost of one large
> > sync'ed write and two smaller sync'ed writes.)
> > open_sync 16k write 242.563 ops/sec
> > 2 open_sync 8k writes 752.752 ops/sec
> >
> > It compares the cost of doing larger vs. two smaller open_sync writes.
> >
>
> Might be some value for determining things like what the optimal WAL
> block size to use is. All these tests are kind of hard to use
> effectively still, I'm not sure if it's time to start trimming tests yet
> until we've made more progress on interpreting results first.
FYI, I beefed up the testing for this in test_fsync:
Compare open_sync with different write sizes:
(This is designed to compare the cost of writing 16k
in different write open_sync sizes.)
1 16k open_sync write 723.824 ops/sec
2 8k open_sync writes 347.979 ops/sec
4 4k open_sync writes 215.114 ops/sec
8 2k open_sync writes 174.613 ops/sec
16 1k open_sync writes 87.496 ops/sec
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2011-01-18 18:51:25 | PgEast: 2011, 2nd call for papers |
Previous Message | Tom Lane | 2011-01-18 18:46:12 | Performance bug in DO blocks |