Uploading folder with wide and deep hierarchy is very slow

[provokateurin]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
When uploading a folder with a wide and deep hierarchy through the web interface, the process of just creating the folder structure takes very long. All requests are run sequentially and the deeper the hierarchy the more requests each folder needs:

Describe the solution you'd like

1. Run some of the requests in parallel (race conditions on the same folder parent should be avoided, but is probably not needed with no. 2)
2. Reduce the overall number of requests:

• The PROPFINDs for /files and /files/<user> can be removed since we can safely assume that they must exist.
• The second PROPFIND for the target folder should not be necessary, since that one returned 404 the first time (yes this could result in a race condition with another requests, but it can already happen anyway and it's not problematic since we just want the folder to exist).
• With Feature/53428 auto create collection on upload #53621 all PROPFINDs can be removed as we can just MKCOL the target directory and it will ignore if any of the parents don't already exist. Even the initial PROPFIND that returns 404 can be removed, as it's cheaper to just always MKCOL instead.

[susnux]

With Feature/53428 auto create collection on upload #53621 all PROPFINDs can be removed as we can just MKCOL the target directory and it will ignore if any of the parents don't already exist. Even the initial PROPFIND that returns 404 can be removed, as it's cheaper to just always MKCOL instead.

No this is not for checking if the folder exists (or only partially) but also to check if the content exists, to check for collisions and open the conflict picker if needed.

[provokateurin]

But the conflict can only happen for files, no? I'd think that those already have a separate PROPFIND before the upload process to detect conflicts. For directories I don't understand why there would be any conflict checking, since we just want the structure to exists regardless if it already existed before or we just created it.

[susnux]

If the directory exists its uploaded inside and needs recursive conflict resolution

[salmart-dev]

Do we have recursive conflict resolution? Currently when trying to upload (drag and drop) a directory which already exists on the server just asks about what to do with the directory itself, but whatever option you select gets applied to every item that gets uploaded, so you can only select to keep the current content, keep both (renames the new dir) or merge/override them, which keeps the content of both but overwrites files with the same name coming from the uploaded directory.