From: James Mansion <james@mansionfamily.plus.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: jd@commandprompt.com, Scott Marlowe <scott.marlowe@gmail.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org, Ben Chobot <bench@silentmedia.com>
Subject: Re: BBU Cache vs. spindles
Date: Sun, 24 Oct 2010 09:05:19 +0100
Message-ID: <4CC3E8BF.4090409@mansionfamily.plus.com> (raw)
In-Reply-To: <4CC0513E0200002500036C68@gw.wicourts.gov>
References: <4CC04EA50200002500036C5E@gw.wicourts.gov>
<201010211935.o9LJZTM21744@momjian.us>
<4CC0513E0200002500036C68@gw.wicourts.gov>
Kevin Grittner wrote:
> On what do you base that assumption? I assume that we send a full
> 8K to the OS cache, and the file system writes disk sectors
> according to its own algorithm. With either platters or BBU cache,
> the data is persisted on fsync; why do you see a risk with one but
> not the other?
>
Surely 'the data is persisted sometime after our write and before the
fsynch returns, but
may be written:
- in small chunks
- out of order
- in an unpredictable way'
When I looked at the internals of TokyoCabinet for example, the design
was flawed but
would be 'fairly robust' so long as mmap'd pages that were dirtied did
not get persisted
until msync, and were then persisted atomically.
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: james@mansionfamily.plus.com, Kevin.Grittner@wicourts.gov, bruce@momjian.us, greg@2ndquadrant.com, scott.marlowe@gmail.com, scrawford@pinpointresearch.com, bench@silentmedia.com
Subject: Re: BBU Cache vs. spindles
In-Reply-To: <4CC3E8BF.4090409@mansionfamily.plus.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