From: "Ragnar Kjørstad" <nfs@ragnark.vestdata.no>
To: "Baker, Byran" <Byran_Baker@bmc.com>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>
Subject: Re: nfs performance problem
Date: Thu, 7 Nov 2002 18:32:06 +0100 [thread overview]
Message-ID: <20021107183206.P23227@vestdata.no> (raw)
In-Reply-To: <CDC5FB5947D3D3119E2D00A0C9B6AF2D06777678@es06-hou.bmc.com>; from Byran_Baker@bmc.com on Thu, Nov 07, 2002 at 09:19:44AM -0600
On Thu, Nov 07, 2002 at 09:19:44AM -0600, Baker, Byran wrote:
> We have a couple of NFS servers with 3ware cards. One is a 3ware 7850 =
(8
> Maxtor 160GB - 5400RPM) and one is a 3ware 7500-12, both configured wit=
h
> RAID 5 + Hot Spare. I have all the latest NFS patches applied. If I a=
ccess
> an NFS mounted directory on one of these systems and copy a bunch of li=
ttle
> files (1-2KB), I get 150-250 tps. If I access larger files (90% > 1MB =
each)
> I will normally see 25-60MB/s transfer with 500-700 tps, with peaks of =
over
> 1000 tps - A good indication that disk seek is to blame for the problem=
with
> the small files.
Just to clarify here.
I bet when you transfer 1-2KB files you are able to transfer 150-250
files pr second, right?=20
When you transfer larger files the files pr second rate goes down, but
the tps-rate increases because each file is split into multiple scsi
requests.=20
And yes, I would agree with your conclution that disk seek is to blame.
Are those numbers for reads or writes? I would expect to see the same
tendency, but with stronger effect, for writes than reads.
--=20
Ragnar Kj=F8rstad
Big Storage
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-11-07 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 15:19 nfs performance problem Baker, Byran
2002-11-07 15:49 ` Matt Heaton
2002-11-07 17:32 ` Ragnar Kjørstad [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-25 14:39 Andreas Schuldei
2007-10-25 13:10 Andreas Schuldei
2007-10-25 13:53 ` Bernd Schubert
2007-10-27 9:25 ` Andreas Schuldei
2007-10-25 15:25 ` Chuck Lever
2007-10-25 19:34 ` Andreas Schuldei
2007-10-26 14:18 ` Chuck Lever
2007-10-26 17:01 ` Talpey, Thomas
2007-10-27 1:35 ` dean hildebrand
[not found] ` <c5befdd30710261835q50d34026h4dad32090db8a084@mail.gmail.co m>
2007-10-29 12:59 ` Talpey, Thomas
2002-11-06 17:08 pwitting
2002-11-05 22:09 Lever, Charles
2002-11-05 20:56 Lever, Charles
2002-11-05 18:03 poczta.dotcom.pl
2002-11-05 19:17 ` Ragnar Kjørstad
2002-11-05 19:55 ` poczta.dotcom.pl
2002-11-05 20:22 ` Matt Heaton
2002-11-05 20:39 ` Benjamin LaHaise
2002-11-05 20:46 ` Matt Heaton
2002-11-05 21:24 ` Benjamin LaHaise
2002-11-05 23:32 ` Ragnar Kjørstad
2002-11-06 8:59 ` myciel
2002-11-06 10:16 ` Ragnar Kjørstad
2002-11-06 11:46 ` myciel
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=20021107183206.P23227@vestdata.no \
--to=nfs@ragnark.vestdata.no \
--cc=Byran_Baker@bmc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox