[
https://issues.apache.org/jira/browse/SLING-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15753982#comment-15753982
]
Timothee Maret commented on SLING-5991:
---------------------------------------
Thanks [~teofili] for looking at this. Indeed, the patch does not contain a
solution for computing the package size.
I did not attempt to solve it because the current state already allow to
evaluate the idea of not buffering the entire package before streaming. From my
micro bench (replicating 1MB, 50MB, 100MB, 250MB, 500MB binary resources), the
time to export the resources is in average 5% shorter with the patch than
without the patch.
I think the patch value is not high enough to justify the added code complexity
and resources consumptions (one thread and one service session per distribution
request) to justify pursuing that direction for the moment. Maybe this could be
a focus later on, assuming the value has increased due to other improvements.
> [SCD] Evaluate avoiding to buffer the whole packages before streaming
> ---------------------------------------------------------------------
>
> Key: SLING-5991
> URL: https://issues.apache.org/jira/browse/SLING-5991
> Project: Sling
> Issue Type: Improvement
> Components: Distribution
> Affects Versions: Content Distribution 0.2.0
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Fix For: Content Distribution 0.2.0
>
> Attachments: SLING-5991.patch
>
>
> As described in SLING-5990, It seems streaming only starts when the whole
> binary is completely buffered (in memory and/or file). The buffering time
> implies a latency which which could be avoided by streaming directly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
