First off, most bittorrent clients show you speed in KiloBYTES, while your
ISP service is listed as KiloBITS.
So if your quoted 768 Kilobits on upload, that's 96 KiloBytes.
Really your probably getting closer to 650 kb upload which is about 80-85 KB
upload.
If your capping at 40KB that's half your upload.
Go the same for your upload, its 6 megaBITS. That's about 768 KiloBytes if
I've got my math anywhere near correct. So at an 80KB cap, your using 1/8th
of your theoretical download. It's probably closer to 1/6th of your download
pipe.
Now you need to get you bittorrent client. I've never used bitcomet, but
check to see if your "limit" is a per client limit, an average limit, or a
hard overall limit.
If it's not limiting the program as a hard limit, than your giving out more
than what your limits are set at. If its an average limit, that means you
could have people pulling in a 2, or 3 times your set limit at any given
moment. It's just supposed to throttle them back to what you set your limit
around. If its a per client limit (which most programs don't have) then you
really could be getting hammered.
-jason
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hey there all. I have a bit of a problem. I have a Netgear WGR614v5
> router, with a 6Mb download and a 768 upload. If I run bitcomet (a
> bittorrent client) on ANY of my machines on the network my latency for
> WoW goes into the red and everything lags several seconds behind.
> Basically it becomes unplayable. Now the odd thing being is that I top
> out at about 80k/sec download, and 40k/sec upload and this still
> happens. I was wondering if you have any ideas to what may be causing
> this?
>
|
Similar Threads
Linear Mode
