[Repost; corrected] It looks to be quite difficult to avoid the issue of Coordination Omission without a major redesign of JMeter.
However, it may be a lot easier to detect when the condition has occurred. This would potentially allow the test settings to be changed to reduce or eliminate the occurrences - e.g. by increasing the number of threads or spreading the load across more JMeter instances. The Constant Throughput Timer calculates the desired wait time, and if this is less than zero - i.e. a sample should already have been generated - it could trigger the creation of a failed Assertion showing the time difference. Would this be sufficient to detect all CO occurrences? If not, what other metric needs to be checked? Even if it is not the only possible cause, would it be useful as a starting point? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
