You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2017/10/02 10:27:01 UTC

[jira] [Commented] (SLING-7142) Allow to pull a set of packages per request

    [ https://issues.apache.org/jira/browse/SLING-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187840#comment-16187840 ] 

Tommaso Teofili commented on SLING-7142:
----------------------------------------

thanks [~marett], it sounds like a possibly nice improvement, but I agree on the code complexity. Maybe we should look at streaming packages in a single requests or directly create "multi packages" (bigger payload). 

> Allow to pull a set of packages per request
> -------------------------------------------
>
>                 Key: SLING-7142
>                 URL: https://issues.apache.org/jira/browse/SLING-7142
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>    Affects Versions: Content Distribution Core 0.2.8
>            Reporter: Timothee Maret
>
> Currently, the sync/reverse agent pull one package per request. 
> This protocol is really simple and it is already possible to decrease the polling interval (via the trigger) to increase the sync throughput. 
> However, establishing a request has a cost which is applied to every packages.
> In order to improve the throughput when processing the queue, we could avoid establishing most of the request, by allowing to pull more than one package per request.
> In order to allow for some flow control, we could let the receiving side define how many packages could be fetched (similarly to how TCP works).
> Allowing to pull more than more package per request adds more complexity to the code, so we may first build a PoC to demonstrate if the improved throughput is worth the added complexity.
> cc [~teofili], [~simone.tripodi]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)