linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Confused by performance
Date: Thu, 27 May 2010 18:45:08 -0700	[thread overview]
Message-ID: <4BFF2024.3040509@noir.com> (raw)
In-Reply-To: <4BFAEABD.2070700@noir.com>

Just as a followup, my problem appears to be hardware related.  It's not 
clear yet whether it's a strange failure mode or a configuration snafoo, 
disk or controller, but elsewhere I'm seeing a btfs single disk 
performance penalty more like 2% over ext[34] which seems completely 
reasonable.

Sorry for the panic.

--rich

  parent reply	other threads:[~2010-05-28  1:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 21:08 Confused by performance K. Richard Pixley
2010-05-25  3:59 ` Mike Fedyk
2010-05-28  1:45 ` K. Richard Pixley [this message]
2010-06-16 18:08   ` K. Richard Pixley
2010-06-16 19:21     ` Roberto Ragusa
     [not found]       ` <AANLkTinM6ab_KEynfgvVT9v5TmcogoLZ0PLAz2oPnsiS@mail.gmail.com>
2010-06-16 19:35         ` Freddie Cash
2010-06-16 19:56           ` Roberto Ragusa
2010-06-17  6:57           ` David Brown
2010-06-16 21:44     ` Daniel J Blueman
2010-06-17  9:57     ` Chris Mason

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=4BFF2024.3040509@noir.com \
    --to=rich@noir.com \
    --cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).