pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Joshua D. Drake <jd@commandprompt.com>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: jason@ohloh.net <jason@ohloh.net>
Cc: Geoff Tolley <geoff@polimetrix.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: SCSI vs SATA
Date: Wed, 04 Apr 2007 08:40:33 -0700
Message-ID: <4613C6F1.3090009@commandprompt.com> (raw )
In-Reply-To: <4613C54C.4050207@kaltenbrunner.cc >
References: <9C0858F5-0A48-4AF9-80FF-E4BA14F0F965@ohloh.net >
<E1HYs6Y-0008O5-SN@elasmtp-banded.atl.sa.earthlink.net >
<E1HYsBX-0006ZE-JG@elasmtp-banded.atl.sa.earthlink.net >
<4613053F.5070401@polimetrix.com >
<DF6C723E-7362-4173-8309-B8AAFC968E2C@ohloh.net >
<4613C14A.4020703@commandprompt.com >
<4613C54C.4050207@kaltenbrunner.cc >
>> SATAII brute forces itself through some of its performance, for
>> example 16MB write cache on each drive.
>
> sure but for any serious usage one either wants to disable that
> cache(and rely on tagged command queuing or how that is called in SATAII
Why? Assuming we have a BBU, why would you turn off the cache?
> world) or rely on the OS/raidcontroller implementing some sort of
> FUA/write barrier feature(which linux for example only does in pretty
> recent kernels)
Sincerely,
Joshua D. Drake
>
>
> Stefan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
view thread (91+ messages) latest in thread
Message-ID: <4613C6F1.3090009@commandprompt.com>
Permalink: ../4613C6F1.3090009@commandprompt.com/
Also on: postgresql.org/message-id/4613C6F1.3090009@commandprompt.com
copy link · copy postgr.es
reply 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: jd@commandprompt.com, stefan@kaltenbrunner.cc, jason@ohloh.net, geoff@polimetrix.com
Subject: Re: SCSI vs SATA
In-Reply-To: <4613C6F1.3090009@commandprompt.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