[
https://issues.apache.org/jira/browse/TS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459274#comment-13459274
]
Alan M. Carroll commented on TS-1457:
-------------------------------------
Yes, I wouldn't expect a lot of difference in memory usage from changing the
chunk size. I view primarily as a CPU optimization and tuning parameter. No one
could explain why 4K chunks were better or worse than any other size so I made
it adjustable.
As for 3.0.2 vs. 3.2 in memory usage in this scenario I don't see anyway to
significantly decrease the memory usage. If the output is being chunked then it
will be buffered and that will consume memory. The only alternative I can see
is to disable keep alive on the connections so that the output is not chunked.
> transforms during video requests cause massive memory growth
> ------------------------------------------------------------
>
> Key: TS-1457
> URL: https://issues.apache.org/jira/browse/TS-1457
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0
> Environment: Linux RHEL6.2
> Reporter: Aidan McGurn
> Assignee: Alan M. Carroll
> Priority: Critical
> Fix For: 3.3.1
>
> Attachments: 3.0.3-null-massif.txt, 3.0.5-null-massif.txt,
> alan-8Kperm-fix-massif.txt, alan-chunk-fix-3.2.0-null.txt,
> alan-nofix-3.2.0-null.txt, alan-NO-fix-massif.txt, alan-perm-fix-massif.txt,
> no-null-3.2.0-massif.txt, null-3.0.2-massif.txt, null-3.2.0-massif.txt,
> ts-1457-patch-1.diff
>
>
> Running the null-transform example object over 3.2.0, shows massive memory
> growth -
> This could be seen on our system since using 3.2.0 with custom plugin which
> invokes transforms - under load ~6K and with video content (only Video -
> small files are ok), a huge growth was seen (GB's) such that it crashes the
> load test machine.
> heap profiles are attached for comparison:
> -null transform example so over 3.2.0
> -NO null transform over 3.2.0
> -null transform example so over 3.0.2
> As can be seen no issue in 3.0.2 -
> The profiles show clearly the call chain is different for both releases
>
--
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
