Doug Orr recommended to us that we give
http://www.chromium.org/developers/telemetry
a shot in generating reproducible web traffic models.
___
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm
On Fri, Apr 18, 2014 at 1:41 PM, Greg White g.wh...@cablelabs.com wrote:
On 4/18/14, 1:05 PM, Dave Taht dave.t...@gmail.com wrote:
On Fri, Apr 18, 2014 at 11:15 AM, Greg White g.wh...@cablelabs.com
wrote:
The choice of RTTs also came from the web traffic captures. I saw
RTTmin=16ms,
Dave,
We used the 25k object size for a short time back in 2012 until we had
resources to build a more advanced model (appendix A). I did a bunch of
captures of real web pages back in 2011 and compared the object size
statistics to models that I'd seen published. Lognormal didn't seem to be
On Fri, Apr 18, 2014 at 11:15 AM, Greg White g.wh...@cablelabs.com wrote:
Dave,
We used the 25k object size for a short time back in 2012 until we had
resources to build a more advanced model (appendix A). I did a bunch of
captures of real web pages back in 2011 and compared the object size
On 4/18/14, 1:05 PM, Dave Taht dave.t...@gmail.com wrote:
On Fri, Apr 18, 2014 at 11:15 AM, Greg White g.wh...@cablelabs.com
wrote:
The choice of RTTs also came from the web traffic captures. I saw
RTTmin=16ms, RTTmean=53.8ms, RTTmax=134ms.
Get a median?
Median value was 62ms.
My own stats
Speaking as the primary Chromium developer in charge of this relevant code,
I would like to caution putting too much trust in the numbers generated.
Any statistical claims about the numbers are probably unreasonable to make.
Reasons:
* We don't actively maintain this code. It's behind the command
On Thu, Apr 17, 2014 at 12:01 PM, William Chan (陈智昌)
willc...@chromium.org wrote:
Speaking as the primary Chromium developer in charge of this relevant code,
I would like to caution putting too much trust in the numbers generated. Any
statistical claims about the numbers are probably
I understand the desire for this code to work, and if I had more bandwidth,
I would definitely fix it sooner. For now, all I can say is, be aware of
the potential issues with the code and use at your own risk. Sorry that we
don't have more bandwidth now to get this working sooner.
On Thu, Apr
