Use s3 storage as the back-end storage, and do not aggregate after uploading to save traffic bandwidth and time.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by tracing Nextcloud’s S3 large-file upload path, especially where segmented data is read back for aggregation and registered in the database. Define how uploads can avoid read-back aggregation, how downloads would handle the segments, and how aggregation error reporting would be configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100