Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Priya M.
8 years agoExplorer | Level 4
Dropbox API to create a file, write in it via stream and then close the file.
Hi,
I am from Softaculous Ltd. I already have an open issue but here I'm opening a new one which is regarding a different issue.
I have a query regarding Dropbox. We want our users to upl...
Greg-DB
Dropbox Community Moderator
8 years agoYour 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.
The chunk size you use will also affect your overall transfer rate though. Smaller chunk sizes will be more robust and less prone to fail, but will be slower overall. Larger chunk sizes will generally be faster overall, as there will be fewer calls and therefore less overhead, but you'd need to re-upload more if any one call fails.
I recommend trying an 8 MB chunk size. The optimal chunk size will depend on various factors though, so you may want to try a few different sizes. Note that you may see some improvement by only using chunk sizes of an example multiple of 4 MB. (This is just due to specifics of how the backend in implemented. There are other factors though, so that improvement may or may not be noticeable.)
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.
The chunk size you use will also affect your overall transfer rate though. Smaller chunk sizes will be more robust and less prone to fail, but will be slower overall. Larger chunk sizes will generally be faster overall, as there will be fewer calls and therefore less overhead, but you'd need to re-upload more if any one call fails.
I recommend trying an 8 MB chunk size. The optimal chunk size will depend on various factors though, so you may want to try a few different sizes. Note that you may see some improvement by only using chunk sizes of an example multiple of 4 MB. (This is just due to specifics of how the backend in implemented. There are other factors though, so that improvement may or may not be noticeable.)
kmeri
8 years agoExplorer | Level 3
where can i get sample for write via stream
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!