From: Christopher Smith <csmith@nighthawkrad.net>
To: nfs@lists.sourceforge.net
Subject: Re: Poor performance (especially writes)
Date: Fri, 08 Dec 2006 18:13:13 +1100 [thread overview]
Message-ID: <45791089.7020804@nighthawkrad.net> (raw)
In-Reply-To: <45786A71.7080908@nighthawkrad.net>
Christopher Smith wrote:
> (Apologies if this is a repost, but I haven't seen it appear four hours
> later and there's no indication the list is moderated...)
>
> Hello, all,
>
> I am having some trouble extracting good (or even average) performance
> out of my NFS server, particular for writes, and was hoping to get some
> suggestions as to how to improve it.
After a day of experimentation, I believe I've nailed this down as being
related to Dell's SAS 5/i disk controller. A regular SATA drive using
the onboard SATA controller in this machine shows about 10x the
performance untarring the smaller image files over NFS.
So, it would appear to be some weird interaction between NFS and Dell's
SAS 5/i disk controller (rebadged LSI device):
02:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X
Fusion-MPT SAS (rev 01)
Subsystem: Dell: Unknown device 1f09
Flags: bus master, 66Mhz, medium devsel, latency 72, IRQ 169
I/O ports at ec00 [disabled] [size=256]
Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
Memory at fe9e0000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at fea00000 [disabled] [size=1M]
Capabilities: [50] Power Management version 2
Capabilities: [98] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
Capabilities: [68] PCI-X non-bridge device.
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
I have duplicated this problem with RHEL installed and reported it to
Red Hat. Anyone else interested ?
--
Christopher Smith
Systems Administrator
Nighthawk Radiology Services
Level 11, Suite 1101
Grosvenor Place
225 George Street
Sydney NSW 2000
Australia
T: 612 - 8211 2300 (IP: x8163)
F: 612 - 8211 2333
M: 61 - 407 397 563
USA Toll free: 866 241 6635
E: csmith@nighthawkrad.net
I: www.nighthawkrad.net
CONFIDENTIALITY NOTICE: This email, including any attachments,
contains information from NightHawk Radiology Services, which may be
confidential or privileged. The information is intended to be for the
use of the individual or entity named above. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this information is prohibited. If you have received
this email in error, please notify NightHawk Radiology Services
immediately by forwarding message to postmaster@nighthawkrad.net and
destroy all electronic and hard copies of the communication, including
attachments.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-12-08 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 19:24 Poor performance (especially writes) Christopher Smith
2006-12-08 7:13 ` Christopher Smith [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=45791089.7020804@nighthawkrad.net \
--to=csmith@nighthawkrad.net \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.