How does duty cycle come into play in server loading work?

Use and application of the eValid server loading (LoadTest) capability. And in the cloud computing context for monitoring and loading.

How does duty cycle come into play in server loading work?

Postby supp » Wed Jun 29, 2011 10:48 am

How does duty cycle come into play in server loading work?
supp
 
Posts: 1
Joined: Wed Jun 29, 2011 10:45 am

Re: How does duty cycle come into play in server loading wor

Postby eValid » Tue Jul 05, 2011 10:29 am

supp wrote:How does duty cycle come into play in server loading work?
The duty cycle of a realistic test is important to know for two reasons: (1) It can help you plan on the resources you need to drive realistic tests; and (2) it can give you leverage on loading that can amplify the work done by your current set of driver machines.

For (1) what you have here is the chance, if the duty cycle is low (assuming that is realistic) to use less-powerful machines to accomplish the loading. Because the duty cycle is low at the time your have 100+ eValid's running in parallel then you'll be using less CPU time.

Accordingly, you can choose a smaller, lower powered machine. Or get more complex scenarios out of the same machine.

For (2), if you know that the duty cycle of one test is, for example, 10%, then if you change the Wait Time Multiplier to 0, which will shoot the duty cycle up to 100%, you ALSO increase the effective imposed load by a factor of 10 as well. Generally it is a 1/(duty-cycle) amplification factor.

This makes your one test -- running now at 100% duty cycle -- look to the server machines like 10 tests (keeping with the 10% example). Same tests, more load imposed, quicker to identify breakpoints or the "knee of the performance curve."

eValid Support
eValid
 
Posts: 2392
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Performance/Load Testing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons