public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Michael Darling <darlingm@gmail.com>, David Chinner <dgc@sgi.com>,
	xfs@oss.sgi.com
Subject: Re: XFS drops create/delete files to 6.6% of EXT3 (software raid) and to 0.6% of EXT3 (3ware hardware raid)
Date: Thu, 24 Apr 2008 10:20:45 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0804241020150.5341@p34.internal.lan> (raw)
In-Reply-To: <481081CE.1080500@sandeen.net>



On Thu, 24 Apr 2008, Eric Sandeen wrote:

> Michael Darling wrote:
>> Eric, for the numbers you provided, are you using a single drive,
>> software raid, or hardware raid?  If a hardware raid, is it a 3ware card?
>
> it's a simple partition on a sata drive.
>
>> I hadn't seen the nobarrier mount option before.  Using that changes
>> sequential creates from about 190/second to about 2500/second, and
>> changes sequential deletes from about 170/second to about 3700/second.
>
> I wasn't recommending, necessarily, that you use it, but was just
> looking for bottlenecks...
>
>> I don't yet have a BBU for the 3ware card, but would certainly get one
>> if we go with the 3ware card before we start putting real data on the
>> raid.  Am I right that with a BBU unit and a battery backup for the
>> server as a whole, that nobarrier would be safe to use?
>>
>> Not using nobarrier, but using logbsize 256k changes sequential creates
>> from about 190/second to about 270/second.  So, it's an improvement, but
>> no where near where a software raid performs (1600/second) or where the
>> hardware raid performs with nobarrier.
>
> Default mkfs & mount w/ 256k logbufs:
>
> xfs,256k logbuf:	1353/s
>
>> On Thu, Apr 24, 2008 at 1:33 AM, David Chinner <dgc@sgi.com
>> <mailto:dgc@sgi.com>> wrote:
>>    > So I played with this a little on 2.6.25, on plain partitions.
>>    >
>>    > I saw similar numbers; for example, sequential creates:
>>    >
>>    > ext3:         23698/s
>>    > xfs:            319/s
>>    > xfs,nobarrier:         4478/s
>>
>>     And with logbsize=256k?
>>
>>     Cheers,
>>
>>     Dave.
>
>

Which program is this that you are using to measure this, bonnie++, or?

  reply	other threads:[~2008-04-24 14:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  1:48 XFS drops create/delete files to 6.6% of EXT3 (software raid) and to 0.6% of EXT3 (3ware hardware raid) Michael Darling
2008-04-24  4:01 ` Eric Sandeen
2008-04-24  5:33   ` David Chinner
2008-04-24  6:23     ` Michael Darling
2008-04-24  6:31       ` David Chinner
2008-04-24 15:39         ` Michael Darling
2008-04-24 12:49       ` Eric Sandeen
2008-04-24 14:20         ` Justin Piszcz [this message]
2008-04-24 14:57           ` Eric Sandeen
2008-04-24 17:18 ` Eric Sandeen
2008-04-25 14:54   ` Michael Darling
2008-04-26 15:23 ` Emmanuel Florac

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=alpine.DEB.1.10.0804241020150.5341@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=darlingm@gmail.com \
    --cc=dgc@sgi.com \
    --cc=sandeen@sandeen.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