Re: [GitHub] [jmeter] vlsi opened a new pull request, #727: Add NoThreadClone to HeaderManager to reduce heap utilization

> HeaderManager should not be shared. Can you elaborate on why HeaderManager should not be shared? A colleague of mine just showed me a heap dump that included ~1'400'000 instances of HeaderManager. Basically, the style of the test plan was to have a HeaderManager under every HttpSampler, so it

Re: [GitHub] [jmeter] vlsi opened a new pull request, #727: Add NoThreadClone to HeaderManager to reduce heap utilization

Hello, Are you sure this does not break existing plans that create Headers dynamically ? HeaderManager should not be shared. Regards On Monday, September 19, 2022, GitBox wrote: > > vlsi opened a new pull request, #727: > URL: https://github.com/apache/jmeter/pull/727 > >## Motivation and

[GitHub] [jmeter] vlsi opened a new pull request, #727: Add NoThreadClone to HeaderManager to reduce heap utilization

vlsi opened a new pull request, #727: URL: https://github.com/apache/jmeter/pull/727 ## Motivation and Context HeaderManager consumes heap, and it looks it can be reused between threads. -- This is an automated message from the Apache Git Service. To respond to the message,