What about only cloning the elements when we actually need to modify them? Or even just agree to never modify them and store the "variable" data in the result instead?

Mike Stover wrote:
A related issue is all that cloning (of test elements) that's happening behind the scenes. I've not yet had time to actually measure, but I have a feeling that it is tremendously expensive -- not the cloning itself, but cleaning up all the garbage afterwards. Anyone got figures?


It's occurred to me on more than one occasion that JMeter could use a TestElement pool that creates objects as needed, or provides currently unused blank objects. It would require changes to code so that TestElements are returned to the pool when done, but it would probably be worth it.

-Mike


Salut,

Jordi.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to