mirror of
https://github.com/nextcloud/server.git
synced 2026-03-01 13:00:44 -05:00
68b9972889
This commit fixes the issue #47856. When you upload a file into a group folder and when you use a single S3 bucket as primary storage, the final move operation hangs for a long time. In the background, Nextcloud initiates a copy-delete sequence from the bucket into the bucket, with causes a lot unnecessary overhead. Nextcloud thinks that the file must be imported to another storage and does not recognize that everything is done on the same object bucket. In that case, the import step can be completely skipped, which saves time, network bandwidth and reduces the load on the object storage. The behavior improves a lot with https://github.com/nextcloud/server/pull/46013. However, there are still some put messages that are being sent to the object storage when you use an object storage as primary storage and upload files into a group folder. Co-authored-by: Kate <26026535+provokateurin@users.noreply.github.com> Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de> |
||
|---|---|---|
| .. | ||
| AppData | ||
| Cache | ||
| Config | ||
| Mount | ||
| Node | ||
| ObjectStore | ||
| Search | ||
| SimpleFS | ||
| Storage | ||
| Stream | ||
| Type | ||
| Utils | ||
| EtagTest.php | ||
| FileInfoTest.php | ||
| FilesystemTest.php | ||
| PathVerificationTest.php | ||
| ViewTest.php | ||