Date: Wed, 4 Apr 2018 15:56:00 -0400 From: Mike Tancsa <mike@sentex.net> To: =?UTF-8?Q?Karli_Sj=c3=b6berg?= <karli@inparadise.se>, freebsd-fs@freebsd.org Subject: Re: Linux NFS client and FreeBSD server strangeness Message-ID: <e0fd9886-8bc7-b4de-acd2-daf73e3e8dc1@sentex.net> In-Reply-To: <C3024CF7-3928-4DBF-9855-82451BDACE01@inparadise.se> References: <369fab06-6213-ba87-cc66-c9829e8a76a0@sentex.net> <2019ee5a-5b2b-853d-98c5-a365940d93b5@madpilot.net> <bc78744a-c668-cbbd-f6fd-0064e7f0dc46@sentex.net> <C3024CF7-3928-4DBF-9855-82451BDACE01@inparadise.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/4/2018 3:44 PM, Karli Sjöberg wrote:
>
> Although I understand it might be difficult for you, it would be interresting to know if a FreeBSD client exhibits the same behaviour. It may be a client problem instead of the server?
I am starting to wonder if its the Linux client's (seeming) massive
write caching, or the way that dump might sputter out data on linux....
It could be causing a certain edge case where the LINUX's NFS client
doesnt bother writing for a while. I do note that the burst is pushing
8-9Gb/s.
doing a straight up cat of /dev/zero to a file over NFS is nice and
steady and works as expected.
FreeBSD dump also works as expected, but then again, the client might
have all sorts of different caching rules that are different
igb1
Kbps in Kbps out
250.20 16.57
16299.44 441.57
121562.3 3267.12
304158.3 8128.84
205250.2 5485.41
159533.5 4294.59
252426.0 6465.67
59065.87 1587.44
109203.0 2935.75
139746.6 3750.78
167724.0 4735.38
96619.25 2597.97
---Mike
--
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e0fd9886-8bc7-b4de-acd2-daf73e3e8dc1>