Steam can do pretty well filling a tail circuit, probably better on average. But a torrent of a large file with a ton of peers when your client has the port forward back into the client absolutely puts more pressure on a tail circuit. More flows makes the shaping work harder.
Sometimes we see an outlier in our reporting and it’s not obvious if a customer has a torrent or a DDoS directed at them for the first few minutes.
Wouldn’t two Steam users downloading a game be enough to notice?
QoS is a thing, so it depends.
Yeah, stream is faster than most Linux torrents in my experience
Steam can do pretty well filling a tail circuit, probably better on average. But a torrent of a large file with a ton of peers when your client has the port forward back into the client absolutely puts more pressure on a tail circuit. More flows makes the shaping work harder.
Sometimes we see an outlier in our reporting and it’s not obvious if a customer has a torrent or a DDoS directed at them for the first few minutes.
Depends. If steam is pulling a full 300mbps on both connections there would still be 40% of the bandwidth available.
No, if two 300 megabit tails are shaped correctly, a third user shouldn’t notice that the 1G backhaul has got a bunch of use going on.
If you do, there’s something wrong or you aren’t really getting the 1G for some reason. Not generally a concern in a carrier platform.