From: "Matt Heaton" <admin@0catch.com>
To: "Baker, Byran" <Byran_Baker@bmc.com>, <nfs@lists.sourceforge.net>
Subject: Re: nfs performance problem
Date: Thu, 7 Nov 2002 08:49:09 -0700 [thread overview]
Message-ID: <08da01c28675$367ea400$6601a8c0@c1886657a> (raw)
In-Reply-To: CDC5FB5947D3D3119E2D00A0C9B6AF2D06777678@es06-hou.bmc.com
I didn't understand? What is a good indication of poor seek time? The high
number for TPS? I thought a high number meant the drive was handling a huge
amount of transactions per second, and not necessarily slow. I would LOVE
to
have my NFS servers push out 500 TPS on iostat. I have 10 webservers that
each ask for between 10-25 files per second from our 3ware 7850 controllers.
We get about 200 TPS on the NFS server. Much more and the clients become
VERY SLUGGISH, and I get blocked R processes in vmstat on the client.
Sometimes
20-40 blocked R processes in vmstat. As soon as I offload some of files
from a busy
NFS server to another NFS server then the clients settle down and everything
works
great again, but I only get 1-1.5MB out of each NFS server before this
happens!
I can get really high TPS out of the server LOCALLY when I do copies etc,
its just
over NFS with a huge amount of really small files that everything stinks.
L8r...
Matt
> 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 with
> RAID 5 + Hot Spare. I have all the latest NFS patches applied. If I
access
> an NFS mounted directory on one of these systems and copy a bunch of
little
> 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.
>
> Thanks,
> -Byran
>
> From: "Matt Heaton" <admin@0catch.com>
> To: "poczta.dotcom.pl" <myciel@dotcom.pl>,
> <nfs@lists.sourceforge.net>
> Subject: Re: [NFS] nfs performance problem
> Date: Tue, 5 Nov 2002 13:22:25 -0700
>
> I have 3ware cards as well (2 7500 Series 8 drive), just like yours. ALso
> with 120 GIG drives (7200)
> RPM. Whever I get 150-200 tps in iostat then my NFS runs SO SLOW. I also
> only get 1 MB, to 1.5 MB
> over NFS. The local speed seems to be ok, not great though. MY OPINION
is
> that this is because of seek time on the raid
> array. I am serving very small files, just like you are. I am
requesting
> about 200-300 files per second from
> each NFS server. So even though our throughput of only 1.5 MB isn't high.
> The number of files per second is
> actually quite high, and causes things to slow down because of seek time
> issues. PLEASE GIVE US CACHEFS SOMEONE??
>
> Does anyone have experience with IDE Raid arrays that get over 250 tps in
> iostat that work fine? I would
> be VERY VERY VERY interested to find out.
>
> L8r...
>
> Matt
>
>
> -------------------------------------------------------
> 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
>
>
-------------------------------------------------------
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 15:49 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 [this message]
2002-11-07 17:32 ` Ragnar Kjørstad
-- 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='08da01c28675$367ea400$6601a8c0@c1886657a' \
--to=admin@0catch.com \
--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