You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Official Dropbox .Net v2 SDK, slow uploading speed for large files
Hello,
We use Official Dropbox .Net v2 SDK.
Average uploading speed for some our clients is 50-100 kb/sec.
We use the following code to upload chunks
log.Trace("{0}. File chunk taken....
The web site uses a somewhat different piece of infrastructure than the API, so that may not be a good comparison.
If you want to test your connection to the Dropbox API content servers directly though, you can test a simpler /2/files/upload API call, e.g., using curl:
https://www.dropbox.com/developers/documentation/http/documentation#files-upload
That would eliminate the complexity of using upload sessions, and let you see what kind of speeds you're getting for a single connection.
Greg-DB
Dropbox Staff
Dropbox StaffFirst, note that the connection speed will vary from place to place. Your connection speed to Dropbox depends on the routing you get between your ISP and our servers, and may be slower than your ISP's rated speeds.
Sometimes resetting or retrying your connection gets you a different route and better speeds, but that is outside of our control. Some ISPs also throttle sustained connections so if you see an initial high connection speed followed by lower speeds, that could be the reason.
Also, I see from the output though that it appears you're using about 2 MB chunks. I recommend using a larger chunk size, such as 8 MB or 16 MB (or even higher, depending on the connection). Using a larger chunk size can increase the overall speed by reducing the number of individual HTTPS requests needed, reducing overhead. It does come at the cost of having to resend more data when any one particular request fails though.
Sometimes resetting or retrying your connection gets you a different route and better speeds, but that is outside of our control. Some ISPs also throttle sustained connections so if you see an initial high connection speed followed by lower speeds, that could be the reason.
Also, I see from the output though that it appears you're using about 2 MB chunks. I recommend using a larger chunk size, such as 8 MB or 16 MB (or even higher, depending on the connection). Using a larger chunk size can increase the overall speed by reducing the number of individual HTTPS requests needed, reducing overhead. It does come at the cost of having to resend more data when any one particular request fails though.
That is all clear, thanks.
But speed is 50 kb/sec...
How can we test the uploading speed to find the error? Should we upload a file via browser and check if the uploading speed is equal?
P.S.
We use a dynamic chunk size. If we receive a timeout error then we start to upload from the beginning with reduced chunk size. By default we upload chunk size = 8 mb.
- Greg-DB
The web site uses a somewhat different piece of infrastructure than the API, so that may not be a good comparison.
If you want to test your connection to the Dropbox API content servers directly though, you can test a simpler /2/files/upload API call, e.g., using curl:
https://www.dropbox.com/developers/documentation/http/documentation#files-upload
That would eliminate the complexity of using upload sessions, and let you see what kind of speeds you're getting for a single connection.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
