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

William Bardwell commented on TS-1457:
--------------------------------------

This is similar possibly identical to some of what I saw in TS-1247.  I will 
experiment with the patch and see if it helps my case.  (I was also needing 
patches in my plugin, especially when the client was much slower than the 
origin, which seems separate from the chunking issue.)
                
> 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

Reply via email to