Status
Not open for further replies.
Torrent is doing about 2.3 MB/sec

The borderless traffic is not being proxied btw... it doesn't explain the low speeds.

Switch off borderless and try again on that torrent. I get 9MB/s here on that on a fibre line using the same breakout pipe as you so no reason you'd see any different.
 
UPLOAD SPEED
3.93 Mb/s
DOWNLOAD SPEED
1.31 Mb/s
Network latency: 386 msec round trip time

Jitter: 52 msec

TEST AGAIN


TCP receive window: 2130432 current, 2195968 maximum
0.07 % of packets lost during test
Round trip time: 383 msec (minimum), 435 msec (maximum), 386 msec (average)
Jitter: -
0.00 seconds spend waiting following a timeout
TCP time-out counter: 589
170 selective acknowledgement packets received

No duplex mismatch condition was detected.
The test did not detect a cable fault.
No network congestion was detected.

0.7482 % of the time was not spent in a receiver limited or sender limited state.
0.0000 % of the time the connection is limited by the client machine's receive buffer.
Optimal receive buffer: - bytes
Bottleneck link: -
158 duplicate ACKs set

170 packets, so that test didn't even get off the ground to start off with. It should test to the local node. With borderless on it won't do that unless you setup some static routing so only way to test and rule out gremlins from another network is to switch off borderless.
 
170 packets, so that test didn't even get off the ground to start off with. It should test to the local node. With borderless on it won't do that unless you setup some static routing so only way to test and rule out gremlins from another network is to switch off borderless.

ok I see it's going to a JNB node now...


UPLOAD SPEED
76.58 Mb/s
DOWNLOAD SPEED
96.53 Mb/s
Network latency: 3 msec round trip time

Jitter: 58 msec

Your system: -
Plugin version: - (-)

TCP receive window: 112384 current, 353280 maximum
0.11 % of packets lost during test
Round trip time: 1 msec (minimum), 59 msec (maximum), 3 msec (average)
Jitter: -
0.00 seconds spend waiting following a timeout
TCP time-out counter: 203
3015 selective acknowledgement packets received

No duplex mismatch condition was detected.
The test did not detect a cable fault.
No network congestion was detected.

0.8781 % of the time was not spent in a receiver limited or sender limited state.
0.0669 % of the time the connection is limited by the client machine's receive buffer.
Optimal receive buffer: - bytes
Bottleneck link: -
2794 duplicate ACKs set
 
torrent speed the same without borderless... :/
 
torrent speed the same without borderless... :/

Full speed here. Test this one and if it remains at that speed try two at the same time. Nothing our side is limiting it and I can't replicate. If anything backhaul is my concern because your local stats seem fine. If both are slow then reboot CPE and your devices. Including the machine so the OS drivers restart.
 
Full speed here. Test this one and if it remains at that speed try two at the same time. Nothing our side is limiting it and I can't replicate. If anything backhaul is my concern because your local stats seem fine. If both are slow then reboot CPE and your devices. Including the machine so the OS drivers restart.

5.5 on the second one. Lemme try the all around reboot
 
Capture.jpg

ok not too shabby with a couple running at once ;)
 
Maybe your torrent client connections isn't setup properly? Run the "setup guide".

EDIT: I set mine up to whatever the global connections it detects but set active torrents to 1 and per torrent same as global.
I barely ever torrent so not really concerned but thanks for the tips. This was more about showcasing the line performance :)
 
Do you think Dave might consider CW's offerings and join the dark side again?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X