Page 1 of 1
Horrible Download Speeds!
Posted: February 18th, 2012, 1:45 am
by Whitechapel
I just upgraded from AT&T to Comcast Xfinity, I'm paying for 15 down and 4 up, and last time I checked I'm getting around 13 down and 4 up, at least that is what my last speed test showed. Here is one I just ran:
Anyway, I'm getting around 100 kb/s down. Using a D-Link 655-DIR, running wireless N and G with the port 119 forwarded to my laptop. When I first started the download it was at 1000 kb/s, then it slowly dropped down and now it wont rise up again and hovers around 100 kb/s. Not using any firewalls or even any antivirus. Windows 7. Is there something I need to configure with my router?
Edit** Right now I'm getting 65 kb/s.
Re: Horrible Download Speeds!
Posted: February 18th, 2012, 2:29 am
by sander
Google "comcast throttling usenet" ...
(BTW: you don't have to forward port 119 to your laptop)
Re: Horrible Download Speeds!
Posted: February 18th, 2012, 11:50 am
by Whitechapel
I read the article, and I quote:
Basically, if your node is congested, and you've been at 85% or more of your down pipe for 15 minutes, then you go into the low priority state for some period of time. Then you come out of it. If the node is congested you'll go right back in after a bit.
The thresholds used (if you visit the pdf linked to in the FAQ above) is 70% of your uplink and/or 80% of your downlink for 15 minutes continuous time.
Sounds like what you're describing. "As of 6 weeks ago" your node became congested.
You can test this by limiting *on your end* usenet download speed to be no more than 75% or so of whatever your down pipe is without speedboost. That should keep you out of this state, leaving a little room for variance or additional use from other apps, and likely will give you overall *faster* average usenet throughput.
Same thing can happen with torrents, or any other long running download. Comcast doesn't care what you're doing, but if your node is congested and you're clogging the tubes for more than 15 minutes, you get sent to the back of the packet bus until the node clears up or you stop flooding it. Self limiting those long running up/downloads keeps you out of the "candidate list".
I did the average of my 3 tests and ended up going with 1152 KB/s, which is what I wasn't even capping at last night and only saw the 1000 KB/s once. Anyway, I did what they said to do there, set my download max to be 1152 KB/s. The average was 14.6MBps but I did it at like 9 to be real safe. That ended up being 1152 KB/s.
Deleted the port forward and I set my download to 1152 KB/s and am getting a little over 100.