It looks like the server closes the connections after every two transactions. I checked the server code - we set the idle timeout to 60 seconds, so the connections should hang around that long for re-use. When I try a test with the rclone serve webdav I see exactly what you see. When I try a test with a nextcloud instance rclone opens -transfers connections and keeps re-using them. I think this is more likely to be a server problem than a client problem. Rclone sets the number of connections to hold on to to -checkers + -transfers + 1 I think, so there should only be 3 persistent connections.
Looking at your wireshark pic I see the same port number repeated so there is some connection re-use but not much - I agree. Not so sure about the server but I think it should be also. Rclone should be using persistent http connections in the client at least. wireshark (shows each request going over a new port):.The rclone config contents with secrets removed. config: ~/bin/rclone config create dav0 webdav url= vendor=other.Rclone WebDAV The command you were trying to run (eg rclone copy /tmp remote:tmp) Which cloud storage system are you using? (eg Google Drive) The same thing happens if you run rclone on both ends, so i'll provide an example with that.Īm I right in guessing that connection:keep-alive / session reuse is not supported over WebDAV? or perhaps I forgot an important flag somewhere? Run the command 'rclone version' and share the full output of the command. And it looks like opening new connections doesn't parallelize, so for really small files you'll get the same transfer speed regardless of how many threads you use (so -transfers 1 -checkers 1 runs at the same speed as -transfers 8 -checkers 8 for instance). Hey! been using rclone to sync stuff to a WebDAV server, which mostly works great love how flexible this thing is!īut, I've noticed that it keeps opening a new http session / tcp connection for every request, which causes a bit of a slowdown. What is the problem you are having with rclone?
0 kommentar(er)
