jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: Coordinated Omission (CO) - possible strategies
Date Thu, 17 Oct 2013 22:29:51 GMT
Hello,
You mean Constant Throughput Timer no ?

Regards
Philippe


On Fri, Oct 18, 2013 at 12:27 AM, sebb <sebbaz@gmail.com> wrote:

> 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 Controller 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: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message