public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Petkus <rpetkus@bnl.gov>
To: xfs@oss.sgi.com
Cc: Petkus Robert <rpetkus@bnl.gov>
Subject: Poor performance -- poor config?
Date: Wed, 20 Jun 2007 16:59:10 -0400	[thread overview]
Message-ID: <4679951E.8050601@bnl.gov> (raw)

Folks,
I'm trying to configure a system (server + DS4700 disk array) that can 
offer the highest performance for our application.  We will be reading 
and writing multiple threads of 1-2GB files with 1MB block sizes.
DS4700 config:
(16) 500 GB SATA disks
(3) 4+1 RAID 5 arrays and (1) hot spare == (3) 2TB LUNs.
(2) RAID arrays are on controller A, (1) RAID array is on controller B.
512k segment size

Server Config:
IBM x3550, 9GB RAM, RHEL 5 x86_64 (2.6.18)
The (3) LUNs are sdb, sdc {both controller A}, sdd {controller B}

My original goal was to use XFS and create a highly optimized config.  
Here is what I came up with:
Create separate partitions for XFS log files: sdd1, sdd2, sdd3 each 150M 
-- 128MB is the maximum allowable XFS log size.
The XFS "stripe unit" (su) = 512k to match the DS4700 segment size
The "stripe width" ( (n-1)*sunit )= swidth=2048k  = sw=4 (a multiple of su)
4k is the max block size allowable on x86_64 since 4k is the max kernel 
page size

[root@~]# mkfs.xfs -l logdev=/dev/sdd1,size=128m -d su=512k -d sw=4 -f 
/dev/sdb
[root@~]#  mount -t xfs -o 
context=system_u:object_r:unconfined_t,noatime,nodiratime,logbufs=8,logdev=/dev/sdd1 
/dev/sdb /data0

And the write performance is lousy compared to ext3 built like so:
[root@~]# mke2fs -j -m 1 -b4096 -E stride=128 /dev/sdc
[root@~]# mount -t ext3 -o 
noatime,nodiratime,context="system_u:object_r:unconfined_t:s0",reservation 
/dev/sdc /data1

What am I missing?

Thanks!

-- 
Robert Petkus
RHIC/USATLAS Computing Facility
Brookhaven National Laboratory
Physics Dept. - Bldg. 510A
Upton, New York 11973

http://www.bnl.gov/RHIC
http://www.acf.bnl.gov

             reply	other threads:[~2007-06-20 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 20:59 Robert Petkus [this message]
2007-06-20 21:04 ` Poor performance -- poor config? Justin Piszcz
2007-06-20 21:16   ` Robert Petkus
2007-06-20 21:23     ` Justin Piszcz
2007-06-21  6:37       ` Sebastian Brings
2007-06-21 23:59         ` David Chinner

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=4679951E.8050601@bnl.gov \
    --to=rpetkus@bnl.gov \
    --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