You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Igor Galić (JIRA)" <ji...@apache.org> on 2013/01/14 18:24:12 UTC
[jira] [Resolved] (TS-1652) 3.2.x - mutexAllocator and
netVCAllocator in-use count continually growing
[ https://issues.apache.org/jira/browse/TS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Galić resolved TS-1652.
----------------------------
Resolution: Fixed
Fix Version/s: (was: 3.3.3)
3.2.3
9f27803fa434e1027798dff17f5454cd56cc6621
> 3.2.x - mutexAllocator and netVCAllocator in-use count continually growing
> --------------------------------------------------------------------------
>
> Key: TS-1652
> URL: https://issues.apache.org/jira/browse/TS-1652
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0
> Reporter: Shaun McGinnity
> Assignee: Alan M. Carroll
> Fix For: 3.2.3
>
>
> Running HTTP traffic through 3.2.0 we see the in-use count from the mutexAllocator and netVCAllocators continually growing.
> An example allocator dump before a test:
> 88064 | 2064 | 688 | memory/netVCAllocator
> 1566720 | 1564800 | 80 | memory/mutexAllocator
> After the test has completed (about 15 minutes of traffic):
> 13914112 | 629520 | 688 | memory/netVCAllocator
> 2570240 | 2376480 | 80 | memory/mutexAllocator
> We never see the in-use counters fall back to the value set before the test. If we start the test again then we get further growth. Running for longer or under heavy load the growth is much clearer:
> 6791976960 | 6791970080 | 80 | memory/mutexAllocator
--
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