From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: New to PostgreSQL, performance considerations
Date: Tue, 12 Dec 2006 17:29:28 -0500
Message-ID: <87hcw0n3xz.fsf@wolfe.cbbrowne.com> (raw)
References: <E1GtolA-0008Fk-4R@elasmtp-banded.atl.sa.earthlink.net>
<20061211173105.GH16692@mathom.us>
<E1Gtplp-0004Ka-GM@elasmtp-junco.atl.sa.earthlink.net>
<20061211184726.GI16692@mathom.us>
<E1GtrB8-0005rw-Iu@elasmtp-kukur.atl.sa.earthlink.net>
<457DA782.3060506@modgraph-usa.com>
<8a0c7af10612111422x6bdcc0c2p7cbfeb5a7b0e0374@mail.gmail.com>
<2FC0D8E7-F8ED-452F-BB13-FB665B516E7F@purefiction.net>
<20061212123252.GR16692@mathom.us>
<42B14BCF-B745-4F94-B5EA-97997744A4D5@purefiction.net>
alex@purefiction.net (Alexander Staubo) wrote:
> On Dec 12, 2006, at 13:32 , Michael Stone wrote:
>
>> On Tue, Dec 12, 2006 at 12:29:29PM +0100, Alexander Staubo wrote:
>>> I suspect the hardware's real maximum performance of the system is
>>> ~150 tps, but that the LSI's write cache is buffering the
>>> writes. I would love to validate this hypothesis, but I'm not
>>> sure how.
>>
>> With fsync off? The write cache shouldn't really matter in that
>> case. (And for this purpose that's probably a reasonable
>> configuration.)
>
> No, fsync=on. The tps values are similarly unstable with fsync=off,
> though -- I'm seeing bursts of high tps values followed by low-tps
> valleys, a kind of staccato flow indicative of a write caching being
> filled up and flushed.
If that seems coincidental with checkpoint flushing, that would be one
of the notable causes of that sort of phenomenon.
You could get more readily comparable numbers either by:
a) Increasing the frequency of checkpoint flushes, so they would be
individually smaller, or
b) Decreasing the frequency so you could exclude it from the time of
the test.
--
output = ("cbbrowne" "@" "gmail.com")
http://cbbrowne.com/info/slony.html
"It can be shown that for any nutty theory, beyond-the-fringe
political view or strange religion there exists a proponent on the
Net. The proof is left as an exercise for your kill-file."
-- Bertil Jonell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: New to PostgreSQL, performance considerations
In-Reply-To: <87hcw0n3xz.fsf@wolfe.cbbrowne.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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