Simone Basso

@gfr10598 you may want to understand why your comment was posted on behalf of @mlab-code-reviews (maybe that's intended behaviour but I still found it rather confusing). > If we get...

> (However, a subsequent test, using much larger outgoing messages showed some activations.) I think there's a PEBCAK here. The variable was set outside the container. So I can't tell...

> 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...

As we discussed in a recent meeting, this looks less scary than `P0`, probably `P1`.

Since we're starting to suspect that this is a platform issue, I think I'm not the best person to be the assignee of this issue. I'm going to assign this...

Now that I understand priorities better, this is probably P3

Also, removing myself because I may not end up being the person doing that

When I fetch https://ndt-iupui-mlab2-mil03.measurement-lab.org/ with chrome, it's using `h2`. Same when I navigate to https://ndt-iupui-mlab2-mil03.measurement-lab.org/static/ndt7.html. Yet Chrome performs the test using secure WebSocket. I believe the browser does not use...

@stephen-soltesz has it been fixed by disabling h2? While it's not breaking clients now, it may break clients in the future when h2 increasingly becomes the norm, for this reason...

Thanks!