Page 1 of 1

eValid doesn't overload the driver machine

PostPosted: Tue Nov 15, 2011 5:38 pm
by kendalla
In a large load, e.g. over 1,000 BUs, how do you make sure that eValid doesn't overload the driver machine?

Re: eValid doesn't overload the driver machine

PostPosted: Wed Nov 16, 2011 2:29 pm
by eValid
kendalla wrote:In a large load, e.g. over 1,000 BUs, how do you make sure that eValid doesn't overload the driver machine?
We have watched this particular performance figure very, very closely.

If you are driving 1,000 BUs from one machine what don't want is to do performance checking on the driver machine...which you would be doing if any resources on it were even closed to saturation.

Our benchmark is a 50% utilization figure: We have overloaded the driver machine if any metric (CPU percent, I/O capacity, etc.) is over 50% of the maximum.

The 50% figure is generally what is seen on the very large cloud instances on which we run 1,000 BU tests. For such scenarios the CPU doesn't go over 50% and the I/O seldom approaches 10%...

If it did, we would open up a new machine (new machine image) and split the driver load 50/50... Et cetera.

eValid Support