On 17-Aug-09, at 7:32 PM, Alan DeKok wrote:
The delay is inter-packet delay. i.e. time between reading two consecutive packets from the detail file.
This code sets the *maximum* delay. It's capped at .25s.
The *minimum* delay is whatever your SQL server can handle.
OK. I did find another problem though. I added some debugging code to confirm this. When you set the load_factor to 100, it caps the delay_time at 1/10th of a second. data->delay_time = (data->srtt * (100 - data->load_factor)) / (data-
load_factor); if (data->delay_time == 0) data->delay_time = USEC / 10;
My debugging code showing the delay time Tue Aug 18 08:19:30 2009 : Info: data->delay_time: 100000 I then set my load_factor to 90, the delay time was far lower. Tue Aug 18 08:21:26 2009 : Info: data->delay_time: 27 Sure setting the load_factor to 100 never is a good idea. But it shouldn't make it slower.