Date: Wed, 10 Oct 2018 22:38:18 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 208130] smbfs is slow because it (apparently) doesn't do any caching/buffering Message-ID: <bug-208130-3630-WqiGpdDp6T@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208130-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-208130-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208130 --- Comment #5 from noah.bergbauer@tum.de --- (In reply to Conrad Meyer from comment #4) If you're talking about sysutils/fusefs-smbnetfs, it maxes out around 8 MB/= s. But I wonder: Why is FreeBSD smbfs capped at about 60 MB/s while Linux cifs (inside bhyve on the same machine!) easily saturates the Gigabit link (120 MB/s)? From a quick peek at the code the maximum read size seems to be 60KB which my measurements somewhat confirm. Synchronously transferring 60KB buf= fers at 60MB/s indicates a round trip time of exactly 1ms - in reality the RTT is 0.35 ms though. Perhaps it takes one time slice for the reply to be process= ed (kern.hz=3D1000)? It's just a bit surprising that remotely mounting a filesystem (or even jus= t a block device) from one freebsd server to another is this hard. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208130-3630-WqiGpdDp6T>