From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mlw <markw(at)mohawksoft(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: benchmarking journalling file systems, fsync, and buffers. |
Date: | 2002-01-12 23:10:58 |
Message-ID: | 22020.1010877058@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
mlw <markw(at)mohawksoft(dot)com> writes:
> I have been doing some benchmarking on RedHat 7.2
I think you neglected to mention the pgbench scale factor?
> Journallng always affects performance. This is no surprise. If you
> have fsync enabled, the affect is less pronounced. (this is also no
> surprise). One interesting thing, as the number of concurrent
> connections goes up, the impact of journalling and fsync are reduced.
If you are approaching the scale factor then that just means that the
backends are spending too much CPU on contending for row locks ...
> I'm not sure of the digestion of all these numbers, but I thought some of you
> guys would be interested in comparing notes.
I find it easier to digest graphs than numbers, so here are a couple of
GIFs of Mark's results. The first is the filesystem/fsync comparison,
the second the NBuffers comparison.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
![]() |
image/gif | 4.8 KB |
![]() |
image/gif | 5.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2002-01-12 23:36:54 | Re: benchmarking journalling file systems, fsync, and buffers. |
Previous Message | Tom Lane | 2002-01-12 20:46:30 | Theory about XLogFlush startup failures |