public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Tom <T-o-m@gmx.net>
Cc: xfs@oss.sgi.com
Subject: Re: Which XFS-options for best performance in my case?
Date: Thu, 02 Oct 2008 10:54:36 -0500	[thread overview]
Message-ID: <48E4EEBC.70105@sandeen.net> (raw)
In-Reply-To: <001d01c92498$a4bd7b40$ee3871c0$@net>

Tom wrote:

> After having fine tuned the RAID-controller and the kernel settings, I am
> reaching the following results: Read 465 MB/s; Write 296 MB/s, which I
> benchmarked with "sync; bonnie++ -u 0 -r 4096 -b -d
> /name_of_the_mounted_partition". These figures are not all to good.

not good based on / compared to what?

First I'd start with direct reads & writes from/to your block device,
see how fast that goes, before you jump up to benchmarking the filesystem.

-Eric

  reply	other threads:[~2008-10-02 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 14:10 Which XFS-options for best performance in my case? Tom
2008-10-02 15:54 ` Eric Sandeen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-02 14:28 Tom

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=48E4EEBC.70105@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=T-o-m@gmx.net \
    --cc=xfs@oss.sgi.com \
    /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