From: Benny Halevy <bhalevy@panasas.com>
To: Krishna Kumar2 <krkumar2@in.ibm.com>
Cc: Peter Staubach <staubach@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: NFS performance degradation of local loopback FS.
Date: Thu, 19 Jun 2008 15:52:42 +0300 [thread overview]
Message-ID: <485A569A.8060601@panasas.com> (raw)
In-Reply-To: <485A4B52.6080504@redhat.com>
On Jun. 19, 2008, 15:04 +0300, Peter Staubach <staubach@redhat.com> wrote:
> Krishna Kumar2 wrote:
>>> 200 processes:
>>>
>> By "200 processes", I meant 200 dd's, each reading from /dev/zero and
>> writing to a file on the filesystem. The script "nfs" was run twice, first
>> with
>> a local filesystem and the second time with the same filesystem NFS
>> mounted.
>>
>>
>
> Well, you aren't exactly comparing apples to apples. The NFS
> client does close-to-open semantics, meaning that it writes
> all modified data to the server on close. The dd commands run
> on the local file system do not. You might trying using
> something which does an fsync before closing so that you are
> making a closer comparison.
try dd conv=fsync ...
Benny
>
> All that said, yes, one would expect a slow down. How much is
> debatable and varies from platform to platform and load to load.
>
> I would also advise care when running NFS like that. It is
> subject to deadlock and is not recommended.
>
> ps
>
>> Thanks,
>>
>> - KK
>>
>> linux-nfs-owner@vger.kernel.org wrote on 06/19/2008 12:16:23 PM:
>>
>>
>>> Hi,
>>>
>>> I am running 2.6.25 kernel on a [4 way, 3.2 x86_64, 4GB] system. The test
>>> is doing I/O on a local ext3 filesystem, and measuring the bandwidth, and
>>> then NFS mounting the filesystem loopback on the same system. I have
>>> configured 64 nfsd's to run. The test script is attached at the bottom.
>>>
>>> My configuration is:
>>> /dev/some-local-disk : /local
>>> NFS mount /local : /nfs
>>>
>>> The result is:
>>> 200 processes:
>>> /local: 108000 KB/s
>>> /nfs: 66000 KB/s: Drop of 40%
>>>
>>> 300 processes (KB/s):
>>> /local: 112000 KB/s
>>> /nfs: 57000 KB/s: Drop of 50%
>>>
>>> I am not using any tuning, though I have tested with both
>>> sunrpc.tcp_slot_table_entries=16 & 128
>>>
>>> Is this big a drop expected for a loopback NFS mount? Any
>>> feedback/suggestions are very
>>> appreciated.
>>>
>>> Thanks,
>>>
>>> - KK
>>>
>>> (See attached file: nfs)[attachment "nfs" deleted by Krishna
>>>
>> Kumar2/India/IBM]
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Benny Halevy
Software Architect
Tel/Fax: +972-3-647-8340
Mobile: +972-54-802-8340
bhalevy@panasas.com
Panasas, Inc.
The Leader in Parallel Storage
www.panasas.com
next prev parent reply other threads:[~2008-06-19 12:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 6:46 NFS performance degradation of local loopback FS Krishna Kumar2
2008-06-19 9:58 ` Krishna Kumar2
2008-06-19 12:04 ` Peter Staubach
2008-06-19 12:52 ` Benny Halevy [this message]
2008-06-20 6:39 ` Krishna Kumar2
2008-06-20 9:21 ` Krishna Kumar2
2008-06-22 8:35 ` Benny Halevy
2008-06-23 8:11 ` Krishna Kumar2
2008-06-23 12:40 ` Benny Halevy
2008-06-26 7:19 ` Krishna Kumar2
2008-06-26 17:42 ` Chuck Lever
2008-06-26 17:55 ` J. Bruce Fields
2008-06-26 21:05 ` Chuck Lever
[not found] ` <76bd70e30806261405g9357c6fg51b973ff076ee78b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-26 21:22 ` kernel hacker's pub night J. Bruce Fields
2008-06-26 21:24 ` J. Bruce Fields
2008-06-27 7:14 ` Benny Halevy
2008-06-27 9:04 ` NFS performance degradation of local loopback FS Krishna Kumar2
2008-06-27 14:06 ` Chuck Lever
[not found] ` <76bd70e30806270706x7cbfd291l6cb6d0cc5e81771-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-30 9:57 ` Krishna Kumar2
2008-06-30 15:25 ` Chuck Lever
[not found] ` <76bd70e30806300825t6490477dpb8ce3ee48a0a6777-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-01 3:43 ` Krishna Kumar2
2008-06-27 17:44 ` J. Bruce Fields
2008-06-27 18:06 ` Dean Hildebrand
2008-06-30 10:10 ` Krishna Kumar2
2008-06-30 15:26 ` Jeff Layton
[not found] ` <20080630112654.012ce3e4-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2008-06-30 15:35 ` J. Bruce Fields
2008-06-30 16:00 ` Chuck Lever
2008-07-01 10:19 ` Krishna Kumar2
2008-07-01 12:47 ` Jeff Layton
2008-06-30 15:35 ` Chuck Lever
2008-07-01 5:07 ` Krishna Kumar2
2008-06-30 15:30 ` Chuck Lever
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=485A569A.8060601@panasas.com \
--to=bhalevy@panasas.com \
--cc=krkumar2@in.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=staubach@redhat.com \
/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