Bandwidth Indicator fluctuating wildly.

[vwgolfman]

Hi,
When UE is downloading (headers or bodies) the bandwidth indicator in the bottom left of the screen fluctuates all over the place.
One second it is 0KB/s then it is 300KB/s then it is 200KB/s etc.

It is as though there is no "sampling" going on. i.e. should it sample the data amount over a 5 second period and then average it to display the rate?

Maybe this is not how it works but it certainly doesn't give me an accurate figure.

Please can anybody throw some light on this?

Many thanks

[alex]

The bandwidth is average over 3 seconds with some smoothering based on previous speed value.

I've checked the code, the problem maybe is the status bar is also updated with recalculating speeds when e.g. saving attachments, so the actual time interval may be less than 3 seconds so the probability of zero bandwidth or other fluctuations in between is increasing.

In the next version it won't recalculate speed in those cases.

Try to verify that the zero appears when the interval between the status bar updates was quick, if so this is the problem.

[vwgolfman]

Hi Alex and thank you for your reply.

Unfortunately I don't think the issue is related to what you describe.

I am currently downloading some large headers (50MB).
The bandwidth indicated in the status bar is showing 200, 320 then 836 then 275 etc. It's all over the place.
It changes every 3 seconds as you say. Occasionally it will have a "short" update i.e. less than 3 seconds but this doesn't necessarily result in a 0KB/s display.

I am running DUMeter at the same time and this is indicating a clear and consistent 360KB/s.
My internet connection cannot run faster than 360KB/s.

Hmmm

[alex]

DuMeter measures bandwidth on the driver level before winsock.

UE is an application so it is after winsock with multiple download threads in a loop, waiting for data to arrive, then reading socket buffer and counting the bytes read at that later point.

So maybe it is winsock buffering plus context switching, I'm not sure why 3 seconds is not enough to smoothen the result.

I think preventing counting bandwidth over very short time intervals will handle zero bandwidth indication.

You may try to set socket buffer size explicitly in properties->tasks and reduce the number of tasks to see if it will result in more even bandwidth indication.