nanog mailing list archives

Re: Proving Gig Speed


From: Matt Erculiani <merculiani () gmail com>
Date: Mon, 16 Jul 2018 13:17:19 -0500

We use Iperf3 for customers that complain about throughput, it's
relatively low overhead compared to the Ookla HTML5 client. Same
scenario as you, we have the tech hook up their laptop to the
customer's drop and perform testing. I suspect your antivirus may be
attempting to perform real-time inspection on the http(s) traffic,
which would crush the little laptop CPU for sure.

Message me off-list and I'll send you a private Iperf3 server IP to test with.

-Matt

On Mon, Jul 16, 2018 at 12:58 PM, Chris Gross
<CGross () ninestarconnect com> wrote:
I'm curious what people here have found as a good standard for providing solid speedtest results to customers. All 
our techs have Dell laptops of various models, but we always hit 100% CPU when doing a Ookla speedtest for a server 
we have on site. So then if you have a customer paying for 600M or 1000M symmetric, they get mad and demand you prove 
it's full speed. At that point we have to roll out different people with JDSU's to test and prove it's functional 
where a Ookla result would substitute fine if we didn't have crummy laptops possibly. Even though from what I can see 
on some google results, we exceed the standards several providers call for.

Most of these complaints come from the typical "power" internet user of course that never actually uses more than 50M 
sustained paying for a residential connection, so running a circuit test on each turn up is uncalled for.

Anyone have any suggestions of the requirements (CPU/RAM/etc) for a laptop that can actually do symmetric gig, a 
rugged small inexpensive device we can roll with instead to prove, or any other weird solution involving ritual 
sacrifice that isn't too offensive to the eyes?


Current thread: