-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-12-22 at 20:04 -0800, L A Walsh wrote:
Carlos E. R. wrote:
Most of the delay in SMB/CIFS I see these days comes from the protocol being cpu bound on either the server or client depending on the application transmission unit and whether it is a reader or writer.
Not good if it is CPU bound.
True -- could be a reason why Win10 disables ethernet device teaming -- the SMB2.1 protocol can't keep up and why SMB3 implements ability for a single file-transfer to be split among multiple TCP connections.
Through SMB2.1 (in Win7), CIFS only uses 1 connection between a server and a client, which limits it to 1 cpu on the receiver and on the sender.
Although, of note, to reach cpu saturation points, my client Win7 is still able to read at 450MB/s and write at 224MB/s (using a 10Gb ethernet limited to 8Gb due both my machines being limited to first generation PCIe bus speeds. Current PCIe bus version is up to 3.x, but both of those machines were still using PCIe 1.x.
A newer client seems to be running about 100MB/s faster on reads ~ 566MB/s.
Both of those are raw device speeds WITHOUT file I/O.
The faster I can go is gigabit cable, anyhow, so all that is above me :-)
Also, prefix NOTE:
Speeds referencing 'Bytes' (capital 'B', use base2 prefixes for consistency, vs. those using 'bits' (lower case 'b' use base10) as Bytes are already a power of 2 (2**3) and mixing a power of 2 unit with power-of-10 prefixes introduces conversion inaccuracies. I note that memory makers referencing sizes in Bytes, also use power of 2(**10) prefixes (KB, MB, GB = 1024, 1024**2, 1024**3), but materials using 'bits' kb, mb, gb refer to power of 10(**3) amounts.
This is incorrect. Units like MB are now always a power of ten, while MiB is a power of two. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpCsvsACgkQtTMYHG2NR9Wj7gCfXKFZbJnQMgphcJi2/dwrHWOx XJUAn3FPliaJJtBmsm5YoOmtyHpLGvm0 =M+aD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org