<div dir="ltr">Justin has signed up for this list, I will just copy the question he sent me directly over at DSLReports and let you chime in with your views.<div><br></div><div>--</div><div><br></div><div><div>I've subscribed to the list.</div><div><br></div><div>Currently the 'saturation' meter is pinging away at an unrelated server (<a href="http://dslreports.com">dslreports.com</a>)</div><div>probably it should ping away, and with higher frequency, at one of the servers streaming data in? because then there are more likely to be filled buffers en-route?</div><div>or are the bloated buffers mainly at the customer end of the experience.</div><div><br></div><div>I can make the saturation meter display RTT directly, and continue during the test as an preference. I don't really want to have it pinging away during the test because it probably slows the result down. Actually I'll have to check that. Definitely on slow lines it would (like GPRS and 3G).</div><div><br></div><div>tcptrace on the server side of one stream would immediately reveal average and peak RTT and more. I wonder if that is the goal to be shooting for rather than these more indirect measurements.</div><div><br></div><div>What is the buffer bloat opinion on the ESNet page?</div><div><br></div><div>»<a href="http://fasterdata.es.net/network-tuning">fasterdata.es.net/network-tuning</a> ··· r-bloat/</div><div><br></div><div>they say more not less buffers are needed for 10gig, and its only a problem with residential. </div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 4:20 PM, Pedro Tumusok <span dir="ltr"><<a href="mailto:pedro.tumusok@gmail.com" target="_blank">pedro.tumusok@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 4:18 PM, Jonathan Morton <span dir="ltr"><<a href="mailto:chromatix99@gmail.com" target="_blank">chromatix99@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On 30 Mar, 2015, at 16:56, Pedro Tumusok <<a href="mailto:pedro.tumusok@gmail.com" target="_blank">pedro.tumusok@gmail.com</a>> wrote:<br>
><br>
> Also would you mind doing another test and share the link for result, so he can check closer?<br>
<br>
</span>I still have the result link for the earlier one:<br>
<br>
<a href="http://www.dslreports.com/speedtest/193440" target="_blank">http://www.dslreports.com/speedtest/193440</a><br>
<br>
Here’s another result without using the webcache, but keeping everything else the same:<br>
<br>
<a href="http://www.dslreports.com/speedtest/199524" target="_blank">http://www.dslreports.com/speedtest/199524</a><br>
<br>
For context, this is through the PowerBook which is running cake, 8Mbps down and 1Mbps up. This is somewhat less than the capacity of the link, but since it’s 3G it varies quite a lot anyway.<br>
<span><br>
> on the other things, yes I'd like to hear about buffer bloat ideas.<br>
<br>
</span>The number-one desirable feature is to carry on measuring the latency while the throughput test is ongoing. This is relevant to anyone who wants to make a VoIP call or play an online game while using the connection for something else. If you have several people in one household, it’s often hard to coordinate their activity to avoid such multitasking.<br>
<span><font color="#888888"><br>
- Jonathan Morton<br>
<br>
</font></span></blockquote></div><br></div></div>I will forward it to him, hopefully he will signup here also, so the smart people can talk to each other and not having me mess it up :)</div><span class=""><div class="gmail_extra"><br></div><div class="gmail_extra"><div><br></div>-- <br><div>Best regards / Mvh<br>Jan Pedro Tumusok<br><br></div>
</div></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Best regards / Mvh<br>Jan Pedro Tumusok<br><br></div>
</div>