octaviand2 commented on issue #5875: URL: https://github.com/apache/jmeter/issues/5875#issuecomment-1538306920
> Frankly speaking, I do not understand the reason to have `recoverRunningVersion` there. > > Apparently, the default implementation in `AbstractTestElement#recoverRunningVersion` iterates over all the properties and calls `org.apache.jmeter.testelement.property.JMeterProperty#recoverRunningVersion`. The test case in the attachment has `HTTP Header Manager` with ~240 headers. > > Of course, it takes time to walk over those 240 properties to reset them. Unfortunataly, `recoverRunningVersion` is there from the beginning: it was added in 2003 in [2e6f30d#diff-436813e2e3a0903a899ea4c44396e9a24ccd045c90e9de50dda8030ec0c44128R78](https://github.com/apache/jmeter/commit/2e6f30d8a083e083553fefe4fb92fd93e7b85d84#diff-436813e2e3a0903a899ea4c44396e9a24ccd045c90e9de50dda8030ec0c44128R78) apparently this is a huge bottleneck for us - our config elements have 300+ properties and the performance is severely limited by these iterations. Any clue on the functional reasoning for it - can it be disabled by some configuration? -- 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-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
