Linux NFS development
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Matt Heaton <admin@0catch.com>
Cc: "poczta.dotcom.pl" <myciel@dotcom.pl>, nfs@lists.sourceforge.net
Subject: Re: nfs performance problem
Date: Tue, 5 Nov 2002 15:39:48 -0500	[thread overview]
Message-ID: <20021105153948.G3934@redhat.com> (raw)
In-Reply-To: <098d01c28509$0df86e20$e2a446a6@user1i6avc9gfx>; from admin@0catch.com on Tue, Nov 05, 2002 at 01:22:25PM -0700

On Tue, Nov 05, 2002 at 01:22:25PM -0700, Matt Heaton wrote:
> 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??

How is cachefs going to help?  The kernel is already trying to cache data 
as much as possible.  Once you're trying to serve more data than you have 
RAM, this are naturally going to degreate quite significantly as the system 
becomes seek bound.

> 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.

Use raid1+0 and you'll be much happier, as read requests will be balanced 
over multiple drives (mirroring means the same data can be read from all 
of the mirrors).  Additionally, you'll have much lower CPU utilization 
and writes won't cause all disks in the array to seek for strip updates.  
Read the archives for the past couple of weeks for another example of the 
performance increase when going from raid5 to raid1+0.

		-ben


-------------------------------------------------------
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

  reply	other threads:[~2002-11-05 20:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 18:03 nfs performance problem 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 20:56 Lever, Charles
2002-11-05 22:09 Lever, Charles
2002-11-06 17:08 pwitting
2002-11-07 15:19 Baker, Byran
2002-11-07 15:49 ` Matt Heaton
2002-11-07 17:32 ` Ragnar Kjørstad
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
2007-10-25 14:39 Andreas Schuldei

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=20021105153948.G3934@redhat.com \
    --to=bcrl@redhat.com \
    --cc=admin@0catch.com \
    --cc=myciel@dotcom.pl \
    --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