Quote Originally Posted by wpte View Post
FTP usually uses streams (as I've told before) which doesn't need that much feedback. Also most of the data processing is done on kernel level and thus does not require much cpu and is faster. This allows the sending side a greater speed.
What you wrote above makes me wonder if you're familiar with sockets and how they are used. For the connected socket it does not matter if FTP or Samba writes 64K data. It just delivers it as a byte stream to the remote end. I have a pretty good guess that a whole 32/64K is given via a single write operation to the TCP stack. And from the moment on it takes ~8ms to finish that operation (in case of 64K). Samba has nothing to do during this time.


Quote Originally Posted by wpte View Post
So yes, I think it's obvious why it's slower, even when I don't really like it
So you say that it's obvious to you why "uploading" (using TCP) via Samba is faster than downloading (also using TCP) even though due to journalling "uploading" requires extra processing and CPU cycles?

If it's so obvious forgive me not commenting any-more what you write as it seems you're not interested in solving this puzzle.