public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@gmail.com>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 2.6.24 Through Linux 2.6.33 Benchmarks
Date: Thu, 11 Mar 2010 20:27:12 +0100	[thread overview]
Message-ID: <20100311202712.58e4d444@gmail.com> (raw)
In-Reply-To: <c1fb08351003101034h17957f4ele0a6cbec085fc434@mail.gmail.com>

On Wed, 10 Mar 2010 20:34:12 +0200
Anca Emanuel <anca.emanuel@gmail.com> wrote:

> In fact, the Linux 2.6.30 kernel
> was 770% faster than its predecessor was and it remained that way with
> the Linux 2.6.31 kernel and then regressed only slightly with the
> Linux 2.6.32 kernel. With the new Linux 2.6.33 kernel, however, the
> PostgreSQL performance atop the EXT3 file-system has fallen off a
> cliff.

The extra performance was just a "bug":

http://www.mail-archive.com/pgsql-performance@postgresql.org/msg34841.html

"[This change] is required for safe behavior with volatile write caches
on drives. You could mount with -o nobarrier and [the performance drop]
would go away, but a sequence like write->fsync->lose power->reboot may
well find your file without the data that you synced, if the drive had
write caches enabled. If you know you have no write cache, or that it
is safely battery backed, then you can mount with -o nobarrier, and not
incur this penalty."

-- 
	Paolo Ornati
	Linux 2.6.33-00001-gbaac35c on x86_64

      reply	other threads:[~2010-03-11 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 18:34 Linux 2.6.24 Through Linux 2.6.33 Benchmarks Anca Emanuel
2010-03-11 19:27 ` Paolo Ornati [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100311202712.58e4d444@gmail.com \
    --to=ornati@gmail.com \
    --cc=anca.emanuel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox