From: "dE ." <de.techno@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: Slow NFS loop performance.
Date: Mon, 26 Nov 2012 21:28:06 +0530 [thread overview]
Message-ID: <50B3918E.4020303@gmail.com> (raw)
In-Reply-To: <20121123172333.GB8776@fieldses.org>
On 11/23/12 22:53, J. Bruce Fields wrote:
> On Fri, Nov 23, 2012 at 04:31:55PM +0530, dE . wrote:
>> 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.
> What exactly is your test?
>
> --b.
Sorry for the late response. I'd 200+ unread mails.
I'm writing a large file to the mounted loop device.
next prev parent reply other threads:[~2012-11-26 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 11:01 Slow NFS loop performance dE .
2012-11-23 17:23 ` J. Bruce Fields
2012-11-26 15:58 ` dE . [this message]
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=50B3918E.4020303@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