From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: more anti-postgresql FUD |
Date: | 2006-10-13 15:35:37 |
Message-ID: | slrneivci9.27so.andrew+nonews@atlantis.supernews.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 2006-10-13, Alexander Staubo <alex(at)purefiction(dot)net> wrote:
> On Oct 13, 2006, at 17:13 , Andrew - Supernews wrote:
>> Your disk probably has write caching enabled. A 10krpm disk should be
>> limiting you to under 170 transactions/sec with a single connection
>> and fsync enabled.
>
> What formula did you use to get to that number?
It's just the number of disk revolutions per second. Without caching, each
WAL flush tends to require a whole revolution unless the on-disk layout of
the filesystem is _very_ strange. You can get multiple commits per WAL
flush if you have many concurrent connections, but with a single connection
that doesn't apply.
> Is there a generic
> way on Linux to turn off (controller-based?) write caching?
I don't use Linux, sorry. Modern SCSI disks seem to ship with WCE=1 on
mode page 8 on the disk, thus enabling evil write caching by default.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomi NA | 2006-10-13 15:36:15 | Re: UTF-8 |
Previous Message | Merlin Moncure | 2006-10-13 15:35:22 | Re: more anti-postgresql FUD |
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Staubo | 2006-10-13 15:43:33 | Re: more anti-postgresql FUD |
Previous Message | Merlin Moncure | 2006-10-13 15:35:22 | Re: more anti-postgresql FUD |