[
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553621#comment-13553621
]
Shashank Gupta commented on SLING-2707:
---------------------------------------
> Do the parallel connections from the uploadclient to CQ map to parallel
> connections to S3 in the datastore implementation? AFAIK S3 is optimized for
> parallel uploads, as each connection might go to a different (internal) S3
> endpoint
The above endpoint has nothing to do with S3. It is ootb CQ load 20 with an
additional servlet endpoint to support chunked file upload into sling. It saves
file chunks into local file system and finally merge them into one file and
save it to crx datastore(filesytem)
> for a reliable test you need a server on a single machine that doesn't do
> anything else, and which has a stable, consistent network connection to the
> client.
I tried the upload test between two machines in my org intranet, the time taken
using single and parallel connections is almost same. But I upload filer over
unreliable internet, I see huge performance gain.
I have attached a testcase and its usage instructions at
https://issues.apache.org/jira/browse/SLING-2707?focusedCommentId=13552658&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13552658
You can run the testcase and observe that using parallel connection increases
the upload speed over internet.
> In *that* case, using parallel connections essentially means abusing server
> resources
imo, by default sling should allow single connection to upload. client should
send special request to sling to use parallel connections and it should be
approved by sling. for e.g. client wanting to upload large file can request
sling to allow it using parallel connections.
> Support of chunked file upload into Sling
> -----------------------------------------
>
> Key: SLING-2707
> URL: https://issues.apache.org/jira/browse/SLING-2707
> Project: Sling
> Issue Type: New Feature
> Components: General
> Reporter: Shashank Gupta
> Attachments: uploadclient.jar
>
>
> Use cases:
> 1. Large file upload - With high speed internet connections, advent of cloud
> and HD going mainstream, Sling should support large files (> 2GB) upload.
> 2. Fault tolerant uploads - Sling should provide capability to resume upload
> from failure point. It should not require client to restart the complete
> upload process.
> 3. Faster upload: Sling should support its clients to initiate multiple
> connection and upload file chunks in parallel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
