Peter Boothe

Possibly addressed by https://github.com/m-lab/ndt-server/pull/285

We welcome pull requests, but have put this issue in our backlog for us to get to as well.

Will fix https://github.com/m-lab/ndt7-client-ios/issues/57

Two subtasks: 1. getting the library tested 2. fixing the underlying problems

The easiest way to determine whether it is GC is to disable GC by running the server with the environment variable `GOGC=off` set and see if the problem is still...

The more I read about things, the more I think it might be `fq_codel` (instead of `fq`) as our qdisc and not Go's GC, but that opinion is based on...

I would still like to try `fq`. `fq_codel` has some smarts that may be inappropriate for our use case. It's normally the right choice, but for our particular case, let's...

This smells to me like a locking problem. What happens if we do all of this while tcp-info is turned off? I hope the same bugs occur, but I worry...

Part of the "validate the platform" KR

Speaking of BBRv2 - https://github.com/google/bbr/blob/v2alpha/net/ipv4/tcp_bbr2.c