Hi all, To all that maybe interested. Gil Tene (from Azul Systems) has started a thread on Coordinated Omissions. it's his name for a problem that I noted in JMeter a while back and for which the current fix is the start threads on demand check box. The problems Gil describes go much deeper than the problems that are due to JMeters current threading model and lack of event based schedulers (which would provide at least a 10x boost in scalability and make it less likely that JMeter will work to hide bottlenecks in your application). The effect of CO is that the test harness becomes like a ref making a bad call at a critical point in the game.
Anyways, I shan't repeat the contents of the thread here. You can find it at [email protected], a mailing list started by Martin Thompson, well known for his work on the Disruptor framework. Regards, Kirk --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
