[
https://issues.apache.org/jira/browse/TS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452476#comment-13452476
]
Leif Hedstrom commented on TS-1457:
-----------------------------------
I've tested v3.0.5 as well, and see similar problems. As far as I can tell from
my tests, with the null-transform, we allocate a substantially large amount of
32KB buffers (which makes sense, it's the hardcoded buffer size in
transforms). These allocations happens on the freelist as normal, and the real
questions are a) why we allocate so many even for a moderate number of
connections and b) why are they not reused efficiently.
One idea could possibly be the sequence number we have in the freelist, it's
16-bit only if I recall. Are we by chance wrapping over or something here? I
don't know what effect that would have, but it's a naieve thought.
> 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: no-null-3.2.0-massif.txt, null-3.0.2-massif.txt,
> null-3.2.0-massif.txt
>
>
> 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
