We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
API moving/renaming of files is slow
At the moment i'm testing the api and noticed if i move multiple files/folder it only moves one file a second. Renaming also suffers from the same problem. This seems rather slow. On the webpage...
Jopo-JP wrote:At the moment i'm testing the api and noticed if i move multiple files/folder it only moves one file a second.
Renaming also suffers from the same problem.
This seems rather slow....
It can cause issues for me, if multiple people at once work on files in dropbox and move stuff around with 100s pdf and this will result in a big wait time.
...
Hi Jopo-JP,
When you say "move multiple files/folders", do you mean batch operation or just single move at a time? 🧐👈 In batch multiple files/folders (up to 1000) can move/rename at once (in border of this second you're talking about). 😉
Hope this helps.
Thanks for the fast response.
It depends on what the user is currently doing and many.
If the user edits a file and saves or rename it, there is no batch operation.
If the other user are doing something similar, they have to technically wait a second.
If a user moves many files, folder in one go, i use the batch operation and after a short time, it gets the job done.
My issues occurs if users try to move smaller files at the same time from different locations, the delay happens.
I might have to flesh my queue system out, so after a threshold has been reached, it should try to categorize it and batch it afterwards.
I though, i wouldn't hit the limit that fast and need to use batch operations this early.
Jopo-JP wrote:...
If the user edits a file and saves or rename it, there is no batch operation.
...Jopo-JP, Save and rename operations cannot execute in batch together, but multiple save (upload actually) operations on one side and multiple rename (move actually) operations on other side can be executed in corresponding batches. Even more if you plane to save a file and rename the same file after that, better save this file at the new name, so you will avoid the rename - one operation less.
Jopo-JP wrote:...
If the other user are doing something similar, they have to technically wait a second.
...To be honest I have no idea of your application design, but when different users use your application on their accounts, there is no any reason one user action to affect any other user (including possible delay if we ignore some corner cases). There is always some way for optimization, but it's closely related to your design (possibly including the steps you mentioned).
Another good direction (if possible for your design) is limiting possibility different users to work on the same namespace as much as possible. Such work predispose conflicts/delays.
Good luck.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
