5 Commits (41fe5d4e29e63a39b7da5848822f117a3d71cd8a)

Author	SHA1	Message	Date
Robin Appelman	aa15f9d16d	chore: run rector ... Signed-off-by: Robin Appelman <robin@icewind.nl>	1 year ago
Ferdinand Thiessen	5981b7eb51	chore: apply new CSFixer rules ... Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de> # Conflicts: # apps/settings/lib/SetupChecks/PhpOpcacheSetup.php	1 year ago
Joas Schilling	5283e9a5e2	test: Cleanup tests/lib/Files/* ... Signed-off-by: Joas Schilling <coding@schilljs.com>	1 year ago
Côme Chilliet	cfca7e7911	fix(tests): Fix most obvious errors in ObjectStore tests ... Some are still failing Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>	2 years ago
Christoph Fiehe	9597072ada	perf(ObjectStoreStorage): Improve (slow) move on same object bucket ... 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>	2 years ago