GotNoRice
[H]F Junkie
- Joined
- Jul 11, 2001
- Messages
- 12,017
I was downloading a torrent tonight and I noticed that my internet was being incredibly slow. I opened up a ping to google and yahoo and both were 1000+. I stopped the torrent and everything went back to normal. Now I have everything setup fine and torrents work awesome. At any given time I’m seeding 150+ torrents and usually downloading one or two. I wanted to see what was going on so I opened up my traffic graph and started the torrent.
After the healthy 20+ meg burst, it pegs at ~8.8 which is what the download cap is. Before, it would usually go back down to around that speed after the burst, but it was never as steady as that. Before, after the burst it would usually just fluctuate between like 7-10 megs. It definitely seems like they changed or implemented something different on their end. I don’t really care that it pegs me at 8.8 after the burst, but why in the world does it destroy my ping times like that?
My router has a traffic shaper of it’s own, and if I enable that and set my own caps just slightly below the Comcast caps, the torrents don’t affect my ping in any way. The downside to this that when I implement my own caps it obviously does not allow bursting.
Before, I didn’t need to use my own traffic shaper, I could benefit from bursting, and it would settle down to a ~8.8 average speed without nerfing my ping. I’m trying to figure out exactly what is going on now, or what changed.
After the healthy 20+ meg burst, it pegs at ~8.8 which is what the download cap is. Before, it would usually go back down to around that speed after the burst, but it was never as steady as that. Before, after the burst it would usually just fluctuate between like 7-10 megs. It definitely seems like they changed or implemented something different on their end. I don’t really care that it pegs me at 8.8 after the burst, but why in the world does it destroy my ping times like that?
My router has a traffic shaper of it’s own, and if I enable that and set my own caps just slightly below the Comcast caps, the torrents don’t affect my ping in any way. The downside to this that when I implement my own caps it obviously does not allow bursting.
Before, I didn’t need to use my own traffic shaper, I could benefit from bursting, and it would settle down to a ~8.8 average speed without nerfing my ping. I’m trying to figure out exactly what is going on now, or what changed.