From: "dE ." <de.techno@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Slow NFS loop performance.
Date: Fri, 23 Nov 2012 16:31:55 +0530 [thread overview]
Message-ID: <50AF57A3.3090000@gmail.com> (raw)
Humm... The last thing I expected was no response even in the mailing list.
So I'm filing a bug on this.
On Oct 23, 2012 2:19 PM, "dE ." <de.techno@gmail.com> wrote:
> Hi!
>
> Great job with NFS server, it surely is fast, but not on loop devices.
>
> If I loop mount a file and share the mount point over NFS3 or NFS4, the
> write performance of the client on the loop mounted share is pretty bad.
>
> On a 100 Mbps (or 12.5MBps) full duplex Ethernet link, I get ~8MBps
> speeds, whereas on the loop mounted device, I get at best 6MBps.
>
> Any ideas why?
>
> My server configuration (NFS4) --
> anonuid=1000,anongid=1000,**secure,no_subtree_check,rw,**fsid=0,crossmnt
>
> My client mount options --
> rsize=1048576,wsize=1048576,**async,hard,timeo=60,retrans=2,**
> actimeo=900,retry=2,**lookupcache=pos,nfsvers=4,**
> nolock,intr,noacl,rdirplus
>
next reply other threads:[~2012-11-23 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 11:01 dE . [this message]
2012-11-23 17:23 ` Slow NFS loop performance J. Bruce Fields
2012-11-26 15:58 ` dE .
2012-11-26 16:08 ` J. Bruce Fields
2012-11-26 16:15 ` dE .
2012-11-26 17:45 ` dE .
2012-11-23 19:04 ` Myklebust, Trond
2012-11-26 16:00 ` dE .
2012-11-26 16:39 ` Myklebust, Trond
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=50AF57A3.3090000@gmail.com \
--to=de.techno@gmail.com \
--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