One issue is that memory never moves between the iobuf sizes. Once a chunk of memory is used for a specific iobuf slot, it's there forever. But unless something is leaking, the total size should eventually plateau, certainly within less than a day if you have a basically constant load. There will be some growth due to blocks being kept in thread local allocation pools, but again that should level in less time than you've run.
On Wednesday, May 24, 2017, 9:50:39 AM CDT, Dunkin, Nick <[email protected]> wrote:#yiv3854814824 #yiv3854814824 -- _filtered #yiv3854814824 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv3854814824 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv3854814824 #yiv3854814824 p.yiv3854814824MsoNormal, #yiv3854814824 li.yiv3854814824MsoNormal, #yiv3854814824 div.yiv3854814824MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv3854814824 a:link, #yiv3854814824 span.yiv3854814824MsoHyperlink {color:blue;text-decoration:underline;}#yiv3854814824 a:visited, #yiv3854814824 span.yiv3854814824MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv3854814824 p.yiv3854814824msonormal, #yiv3854814824 li.yiv3854814824msonormal, #yiv3854814824 div.yiv3854814824msonormal {margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv3854814824 p.yiv3854814824msochpdefault, #yiv3854814824 li.yiv3854814824msochpdefault, #yiv3854814824 div.yiv3854814824msochpdefault {margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv3854814824 span.yiv3854814824msohyperlink {}#yiv3854814824 span.yiv3854814824msohyperlinkfollowed {}#yiv3854814824 span.yiv3854814824emailstyle17 {}#yiv3854814824 span.yiv3854814824msoins {}#yiv3854814824 p.yiv3854814824msonormal1, #yiv3854814824 li.yiv3854814824msonormal1, #yiv3854814824 div.yiv3854814824msonormal1 {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:Calibri;}#yiv3854814824 span.yiv3854814824msohyperlink1 {color:#0563C1;text-decoration:underline;}#yiv3854814824 span.yiv3854814824msohyperlinkfollowed1 {color:#954F72;text-decoration:underline;}#yiv3854814824 span.yiv3854814824emailstyle171 {font-family:Calibri;color:windowtext;}#yiv3854814824 span.yiv3854814824msoins1 {color:teal;text-decoration:underline;}#yiv3854814824 p.yiv3854814824msochpdefault1, #yiv3854814824 li.yiv3854814824msochpdefault1, #yiv3854814824 div.yiv3854814824msochpdefault1 {margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:Calibri;}#yiv3854814824 span.yiv3854814824EmailStyle29 {font-family:Calibri;color:windowtext;}#yiv3854814824 span.yiv3854814824msoIns {text-decoration:underline;color:teal;}#yiv3854814824 .yiv3854814824MsoChpDefault {font-size:10.0pt;} _filtered #yiv3854814824 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv3854814824 div.yiv3854814824WordSection1 {}#yiv3854814824 Hi Alan, This is 7.0.0 I only see this behavior on ioBufAllocator[0], [4] and [5]. The other ioBufAllocators’ usage looks as I would expect (i.e. allocated goes up then flat), so I was thinking it was more likely something to do with my configuration or use-case. I’d also just like to understand, at a high level, how the ioBufAllocators are used. Thanks, Nick From: Alan Carroll <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, May 24, 2017 at 10:33 AM To: "[email protected]" <[email protected]> Subject: Re: Understanding ioBufAllocator behvaiour Honestly it sounds like a leak. Can you specify which version of Traffic Server this is? On Wednesday, May 24, 2017, 8:22:46 AM CDT, Dunkin, Nick <[email protected]> wrote: Hi I have a load test that I’ve been running for a number of days now. I’m using the memory dump logging in traffic.out and I’m trying to understand how Traffic Server allocates and reuses memory. I’m still quite new to Traffic Server. Nearly all of the memory traces look as I would expect, i.e. memory is allocated and reused over the lifetime of the test. However my readings from ioBufAllocator[0] show a continual increase in allocated AND used. I am attaching a graph. (FYI – This graph covers approximately 3 days of continual load test.) I would have expected to start seeing reuse in ioBufAllocator by now, like I do in the other ioBufAllocators. Can someone help me understand what I’m seeing? Many thanks, Nick Dunkin Nick Dunkin Principal Engineer o: 678.258.4071 e: [email protected] 4375 River Green Pkwy # 100, Duluth, GA 30096, USA
