From a3d027c87d805667d69372fe6be9cd2a8378efed Mon Sep 17 00:00:00 2001 From: Josh Date: Mon, 8 Apr 2024 18:47:21 -0400 Subject: [PATCH] docs(admin): Document MultipartUpload for uploading chunks to s3 Add a note to the "Large file upload on object storage" section. Signed-off-by: Josh --- .../configuration_files/big_file_upload_configuration.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/admin_manual/configuration_files/big_file_upload_configuration.rst b/admin_manual/configuration_files/big_file_upload_configuration.rst index af52cb4126c..f83a15ba453 100644 --- a/admin_manual/configuration_files/big_file_upload_configuration.rst +++ b/admin_manual/configuration_files/big_file_upload_configuration.rst @@ -174,6 +174,8 @@ to the actual file on the Nextcloud servers temporary directory. It is recommend the size of your temp directory accordingly and also ensure that request timeouts are high enough for PHP, webservers or any load balancers involved. +.. tip:: In more recent versions of Nextcloud Server, when uploading to S3 in *Primary Storage* mode, we use S3 `MultipartUpload`. This allows chunked upload streaming of the chunks directly to S3 so that the final MOVE request no longer needs to assemble the final file on the Nextcloud server. This requires your ``memcache.distributed`` to be set to use Redis (or Memcached), otherwise we fall back on the prior behavior which consumes space on the Nextcloud Server for file assembly (as described above). + Federated Cloud Sharing -----------------------