dexter wrote:The mechanism was designed before consumer 100mbps connections existed. If you run fewer connections other applications will get more slices of available bandwidth. That's all I can suggest for now.
Ahhh, that's annoying, but workaround-able. Though, out of curiousity, how on earth could it work reliably < 20mb but at the same time be unable to differentiate the speeds above 20Mb? (e.g. if I set the limited at 20, it stays at 20, at 15 it stays at 15 etc (+/- 1 mb) ) was it just more expedient way back when to hardcode a maximum speed limit to the throttling routine rather than spy on the reported throughput for the connection, or is it something else?