Use s3 storage as the back-end storage, and do not aggregate after uploading to save traffic bandwidth and time. #59169
Description
Hello, everyone,
Recently, Nextcloud uses s3 storage backend. When uploading large files (more than 1G), it was found that nextcloud would read back the content of s3 to achieve aggregation. However, this would take a lot of traffic and time, and even lead to system timeout.
Can we not read back and register these segmented data directly in the database, and then aggregate them in some way when users download them later?
It is also best to reduce this aggregation error reporting through configuration, but configuration through search, AI and other methods is not enough.
Uploading large files will cause timeout in the aggregation process