Saint Petersburg, FL
said by iansltx:It's not that simple my friend. I and many others have tried to work around PB in broadband benchmarking and it's extremely difficult and differs like I said earlier with each provider. It also tends to cause havoc with streaming and other applications where the streaming engine is inferior or intolerant of wide datarate fluctuations and/or slower or misconfigured PC's. Simply put PB is great for marketing and real crappy for real world performance where consistency of datarate is important.
PowerBoost may still be in effect 30 seconds after a multistream download starts. After PB dies speeds are roughly as advertised *shrugs*
"I cant give you a surefire formula for success, but I can give you a formula for failure: try to please everybody all the time."
~ Herbert Bayard Swope
Comcast's implementation is a "leaky token bucket" shaper, which is over all flows on the user. Since the burst capacity is generally around ~20 MB of data, this should be gone after 10-15 seconds at the data rates we are talking about, so at least for Comcast the measurements are highly likely to exclude powerboost effects.
Additionally, this is data which, IIRC, is or will be made available, including packet traces, through Mlabs. If so, you can validate for yourself that the sustained data rate has dropped down, excluding the burst effects.
And this may make consistent datarate apps unhappy (OTOH, constant datarate apps need to adapt anyway because of cross-traffic), but it makes bursty-interactive apps, like web surfing, very happy.