https://bugs.kde.org/show_bug.cgi?id=291835
--- Comment #47 from [email protected] <[email protected]> --- @Nate Graham Yes, those were my pragmatic conclusions too. I think the buffer tunable is possible, but it's a cludge. The real issue is network latency and the fact that each 64kB block takes an amount of time to transfer which is comparable to network latency: from the gnome thread: https://bugzilla.gnome.org/show_bug.cgi?id=776339#c21 > Interestingly my ping time to the server is 0.7ms and at 100MByte/s a > 64kb buffer would theoretically take 0.625ms, so we can see how round > trip time can quickly become significant It gets much worse over wireless or other higher latency networks. So the next block must be requested and already on it's way before the first block finishes xfer. That's the solution, and that's what mount-cifs does. Since I stopped looking at this 12 months ago, I have been using an fstab mount using mount.cifs for those smb shares where throughput matters. mount.cifs flies. Always at 95% of wirespeed, or better. -- You are receiving this mail because: You are watching all bug changes.
