Federated shares shouldn't be able to slow down NC as much

[theCalcaholic]

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 (especially larger) federated shares from other NC instances are within a directory, loading of the directory content will not terminate before the shared directory is fetched (probably mainly metadata, like size, modified date) as well. This can lead to long loading times, or, in the worst case, timeouts and a blank page.

Describe the solution you'd like I'd propose the following solution: Shares could be displayed without metadata. Metadata could be loaded in a subsequent, non-blocking request.

Additional context I'm currently on NC 22.2.2

[PVasileff]

Hello, I have linked two nexcloud servers with federated shares before a year ago.

When we try to view 'shared with me' folder that shared with federated share - page loading maybe after 10 - 15 - 20 sec.

Both nextcloud running at latest version: Nextcloud Hub II (23.0.4) They running on debian 11, nginx, mariadb 10.5, php 8.0. Both NC are not crypted.

Me and my friend sharing folders each athoer with images, we heve a gigabit network line (each from different isp), a lot of cpus and memory on vms that running NC servers.

So the problem not in connectivity between us or server resources.

[joshtrichards]

This also occurs with External Storage IIRC.