https://bugs.kde.org/show_bug.cgi?id=291835
oli...@openbrackets.net <oli...@openbrackets.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oli...@openbrackets.net
--- Comment #40 from oli...@openbrackets.net <oli...@openbrackets.net> ---
If it's any consoloation, they are having exactly the same discussion over at
gnome-gvfs:
https://bugzilla.gnome.org/show_bug.cgi?id=776339
I did a bunch of recompiling with different buffer sizes over there. For my
case 4MB+ buffers give good read speed (wire speed 100MB/s). I haven't dealt
with the write case yet for gvfs, as the code is very different.
Conclusion as far as I see (for gvfs AND kioslave) is one of these:
1. short-term: make a tunable config variable available so people can grow
their buffer sizes to max out their wires. (I totally understand and agree with
the devs that just hard coding a huge size is not really acceptable). Hopefully
this works for write as well as read (read is proven).
2. medium-term: this comment:
https://bugs.kde.org/show_bug.cgi?id=291835#c26
sounds the most primising to me, ie UNDERSTAND how cifs manages to be proper
fast (presumably) without huge buffer sizes (eg pre-request 2x64kB for
read..something similar for write..?)
I am happy to help if the kioslave devs can agree with the above strategy?
Opinions?
--
You are receiving this mail because:
You are watching all bug changes.
