Linux NFS development
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>
To: Gabriel Barazer <gabriel-KSe8qvLY914@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS performance (Currently 2.6.20)
Date: Wed, 06 Feb 2008 21:24:41 +0100	[thread overview]
Message-ID: <47AA1789.2040007@krogh.cc> (raw)
In-Reply-To: <47AA12C5.4010807-KSe8qvLY914@public.gmane.org>

Gabriel Barazer wrote:
> On 02/06/2008 4:59:39 PM +0100, "Jesper Krogh" <jesper-Q2TZfHgGEy4@public.gmane.org> wrote:
> 
>>> I have a similar setup, and I'm very curious on how you can read an
>>> "iowait" value from the clients: On my nodes (server 2.6.21.5/clients
>>> 2.6.23.14), the iowait counter is only incremented when dealing with
>>> block devices, and since my nodes are diskless my iowait is near 0%.
>>
>> Output in top is like this:
>> top - 16:51:01 up 119 days,  6:10,  1 user,  load average: 2.09, 2.00, 
>> 1.41
>> Tasks:  74 total,   2 running,  72 sleeping,   0 stopped,   0 zombie
>> Cpu(s):  0.2%us,  0.0%sy,  0.0%ni, 50.0%id, 49.8%wa,  0.0%hi,  0.0%si, 
>> 0.0%st
>> Mem:   2060188k total,  2047488k used,    12700k free,     2988k buffers
>> Swap:  4200988k total,    42776k used,  4158212k free,  1985500k cached
> 
> You have obviously a block device on your nodes, so I suspect that 
> something is reading/writing to it. Looking at how much memory is used, 
> your system must be constantly swapping. This could explain why your 
> iowait is so high (if your swap space is a block device or a file on a 
> block device. You don't use swap over NFS do you?)

No swap over NFS and no swapping at all.

A "vmstat 1" output of the above situation looks like:
procs -----------memory---------- ---swap-- -----io---- -system-- 
----cpu----
  0  2  42768  11580   1368 1987336    0    0     0     0  638  366  1 
0 50 48
  0  2  42768  13088   1368 1985924    0    0     0     0  695  367  2 
1 50 47
  0  2  42768  13028   1368 1986112    0    0     0     0  345  129  0 
0 50 50
  1  1  42768  12720   1364 1986328    0    0     0     0 1043  710  6 
1 50 42
  0  1  42768  12648   1364 1987308    0    0     0     0  636  374  2 
4 50 44
  0  2  42768  11608   1364 1988436    0    0     0     0  696  382  1 
0 51 49

You can also see that there barely is used any swap in the "top" report.

Jesper
-- 
Jesper

      parent reply	other threads:[~2008-02-06 20:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 10:04 NFS performance (Currently 2.6.20) Jesper Krogh
     [not found] ` <3093.195.41.66.226.1202292274.squirrel-e3PW5SUo3N5/BLzvFphCflpr/1R2p/CL@public.gmane.org>
2008-02-06 14:37   ` Gabriel Barazer
     [not found]     ` <47A9C620.70106-KSe8qvLY914@public.gmane.org>
2008-02-06 15:18       ` Trond Myklebust
     [not found]         ` <1202311096.12647.28.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-06 18:24           ` Gabriel Barazer
     [not found]             ` <47A9FB75.90206-KSe8qvLY914@public.gmane.org>
2008-02-06 18:46               ` Trond Myklebust
2008-02-06 15:59       ` Jesper Krogh
     [not found]         ` <64226.195.41.66.226.1202313579.squirrel-e3PW5SUo3N5/BLzvFphCflpr/1R2p/CL@public.gmane.org>
2008-02-06 20:04           ` Gabriel Barazer
     [not found]             ` <47AA12C5.4010807-KSe8qvLY914@public.gmane.org>
2008-02-06 20:24               ` Jesper Krogh [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=47AA1789.2040007@krogh.cc \
    --to=jesper-q2tzfhggey4@public.gmane.org \
    --cc=gabriel-KSe8qvLY914@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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