[
https://issues.apache.org/jira/browse/TS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454958#comment-13454958
]
Alan M. Carroll commented on TS-1457:
-------------------------------------
I think that means I understand the issue. My own testing indicates that
tweaking down the dechunked_buffer as noted in my previous comment has
measurable effects. It would be interesting for you to try that as well but I
think these results are sufficiently indicative to conclude that I've got it
basically cracked. I'll work on getting this polished up and committed.
With regard to the 3.0.2 numbers I would think that this is simply going to be
a bit worse because it is now dechunking and chunking for transforms. How did
that work in 3.0.2? Did the plugins have to handle the chunking themselves in
the stream? What is the behavioral difference from the plugin point of view to
the change in chunking handling from 3.0.2 to 3.0.3?
> 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
> Priority: Critical
> Attachments: 3.0.3-null-massif.txt, 3.0.5-null-massif.txt,
> alan-chunk-fix-3.2.0-null.txt, alan-nofix-3.2.0-null.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
