[GitHub] [jmeter] FSchumacher commented on issue #5875: Performance affected by Config Elements

["FSchumacher (via GitHub)" <gi...@apache.org>]

FSchumacher commented on issue #5875:
URL: https://github.com/apache/jmeter/issues/5875#issuecomment-1533285150

   Well, to get a real insight, look at the source :)
   That said, I looked at the source (not for the first time) and am always a bit confused by it :)
   So, the header element has to be prepared by the thread group, as it doesn't know, whether it will be used, or not. That preparation is eating up a lot of CPU cycles, especially, as the list of headers is quite big.
   The iteration over all those entries is stressing the memory system (GC) a bit, so that is consuming CPU cycles, too.
   In my shallow profiling attempt for this test plan I saw, that `CollectionProperty#recoverRunningVersion` crept up in the methods.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org