On Wed, Aug 31, 2016 at 10:04 AM, Vladimir Sitnikov < [email protected]> wrote:
> UBIK>The issue with CTT is that it tries to match the throughput but always > exceeds it before slowing down, and if CTT is combined with variable pauses > UBIK>, it becomes very hard for CTT to adjust the pauses to reach the > Throughput.. > > If CTT has issues, why don't we just fix CTT then? > Because it is probably impossible. CTT has use cases but does not fit here due to variable pauses I think. That's why we need this additional feature. > Do you mean CTT will never be able to follow given throughput goal? > It will but the more pauses are variable the harder it is for it. > Well, the timer of my choice does follow given throughput with no > overshooting/undershooting issues, so it is not that big deal to have a > timer that just follows given throughput goal. > > Note: CTT is off-topic for the current thread. > No, because you mentioned in the bugzilla CTT as being able to answer this use case. That's why I am mentionning it. Note2: Philippe has recently fixed a couple of issues around CTT, thread > pausing, etc. > Yes, but it only concerns the stopping of the test. > > Note3: I agree there might be valid cases for "adjust interpage timers" > feature. > Good thing :-) We're almost okay then :-) > > Vladimir > -- Regards Ubik Load Pack <http://ubikloadpack.com> Team Follow us on Twitter <http://twitter.com/ubikloadpack> Cordialement L'équipe Ubik Load Pack <http://ubikloadpack.com> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
