From: Greg Smith <greg@2ndquadrant.com>
To: Jignesh Shah <jkshah@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL as a local in-memory cache
Date: Thu, 01 Jul 2010 06:00:01 -0400
Message-ID: <4C2C6721.2010000@2ndquadrant.com> (raw)
In-Reply-To: <AANLkTiljNjw1EIpqWbhXTJZyYPJ7Vb3jsvEmA9NUv9Ys@mail.gmail.com>
References: <AANLkTikj3pglP8uqPdUBHZ3bDQq86aG6MYzDUUyurTez@mail.gmail.com>
<201006300139.o5U1dHN12285@momjian.us>
<AANLkTiljNjw1EIpqWbhXTJZyYPJ7Vb3jsvEmA9NUv9Ys@mail.gmail.com>
On 6/30/2010 2:21 PM, Jignesh Shah wrote:
> If the underlying WAL disk is SSD then it seems I can get
> synchronous_commit=on to work faster than
> synchronous_commit=off..
The first explanation that pops to mind is that synchronous_commit is
writing all the time, which doesn't have the same sort of penalty on
SSD. Whereas if you turn it off, then there are some idle periods where
the SSD could be writing usefully, but instead it's buffering for the
next burst instead. The importance of that can be magnified on
operating systems that do their own buffering and tend to lag behind
writes until they see an fsync call, like is the case on Linux with ext3.
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: greg@2ndquadrant.com, jkshah@gmail.com, bruce@momjian.us, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, dfontaine@hi-media.com, josh@agliodbs.com
Subject: Re: PostgreSQL as a local in-memory cache
In-Reply-To: <4C2C6721.2010000@2ndquadrant.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