If you use a transmission client (e.g.), you can change the upload speed of your client. Do one test at a low upload speed (5K/second), and one test just above your ISP's advertised upload speed.
In the first case you should see your speed peak out around 850mb/s. In the second, if you have a bufferbloat situation, the download speed will drop significantly as the uploads push the download acks into a queue, forcing TCP to throttle heavily downwards.
But only when I’m downloading new games off Xbox one. Finishes in minutes rather than 10s of minutes.
The anti-buffer bloat stuff from the recent DOCSIS (I forget if it was 3.0 or the one after) are supposed to help a LOT with latency issues. Not as good as fiber but close enough that global distance issues become dominant again.
There's a lot of reason to believe this is true.
I noticed that in some ping tests when I had a cable modem, RTT went to over 3 seconds for a ping to google when the uplink was saturated.
https://fgiesen.wordpress.com/2018/01/20/network-latencies-a...
I changed from 50Mb/s to 1000Mb/s service a few months ago; latency is much the same, which means that when the pipe is not crowded, I really can't tell the difference.
(But it's wonderful headroom for large file transfers.)