It sounds like his router is flooded by P2P connections.

VM doesn't shape P2P 24/7.

In reply to a post by Zadeks:

It sounds like his router is flooded by P2P connections.

VM doesn't shape P2P 24/7.

ACTUALLY I was thinking that it sounds like he hasnt got it set up right.. I dont mind downloading overnight.. but it would be nice to have some KB/s during peak in case I see something I want instantly..

Also, if he saturates his upstream, it will slow down all Internet traffic.

I often see 500KB/s+ from VM peers during peak hours.

if you upload faster then 150KB/s download speed can gets affected (from what i have seen on my connection)

just set the upload to 100KB/s or lower (also having the firewall options enabled on the Virgin Hub or Superhub can affect download speed or crash the modem when under p2p load, just untick them as the basic firewall works fine)

In reply to a post by paulb100:

Iam being screwed over by SKY LLu - going from a 19Mb connection with BT & o2 to a whopping 3Mb connection with peak-time slowdown on SKY LLu SVBN Broadband Unlimited...

Iam thinking about moving to Virgin Cable , Iam a lite P2P user, can anyone tell me what speed Bit-torrent is restricted to during the peak hours of 10am-9pm..? is it 25kbps / 50kbps / 100kbps...?? just what is it? i tried contacting virgin but they could not give me an answer

any info would be great

thanks

During the managed hours the downstream traffic goes into a 'bad boy pipe' along with all the rest of the P2P and Usenet traffic, this is allocated 25% of the downstream capacity in your area as a maximum, which is between 50Mb and 100Mb depending on the number of channels in use, 4 will give 50Mb, 6 gives 75Mb, and a full 8 leaves 100Mb for P2P/Usenet.

The more people that are using P2P and Usenet on your port the smaller your share will be and the slower your speeds will be.

In addition if non-P2P traffic is using over 75% of the bandwidth it takes priority and will edge out P2P/Usenet.

You will see full speeds from VM peers due to how VM operate the shaping, they tag traffic just after the entry points to their network, as VM peers don't go through the tagging hardware traffic from other VM peers isn't throttled.

This applies to upstream too, if it's to other VM connections it's fine, if it leaves the VM network it'll get pretty brutally throttled.

Edited by deleted (Sat 14-Apr-12 22:19:12)

In reply to a post by paulb100:

thanks for the insight leexgx

whats latency like?

Piece of string question, all depends on your local area. From what I can tell mine is 'average'.

PING www.bbc.net.uk (212.58.246.94): 32 data bytes

40 bytes from 212.58.246.94: icmp_seq=0 ttl=53 time=12.1 ms
40 bytes from 212.58.246.94: icmp_seq=1 ttl=53 time=13.6 ms
40 bytes from 212.58.246.94: icmp_seq=2 ttl=53 time=21.1 ms
40 bytes from 212.58.246.94: icmp_seq=3 ttl=53 time=13.5 ms
40 bytes from 212.58.246.94: icmp_seq=4 ttl=53 time=14.7 ms
40 bytes from 212.58.246.94: icmp_seq=5 ttl=53 time=13.7 ms
40 bytes from 212.58.246.94: icmp_seq=6 ttl=53 time=13.4 ms
40 bytes from 212.58.246.94: icmp_seq=7 ttl=53 time=17.5 ms
40 bytes from 212.58.246.94: icmp_seq=8 ttl=53 time=13.3 ms
40 bytes from 212.58.246.94: icmp_seq=9 ttl=53 time=14.4 ms

--- www.bbc.net.uk ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max = 12.1/14.7/21.1 ms

A different length piece of string..

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=9ms TTL=54
Reply from 212.58.244.68: bytes=32 time=7ms TTL=54
Reply from 212.58.244.68: bytes=32 time=10ms TTL=54
Reply from 212.58.244.68: bytes=32 time=9ms TTL=54
Reply from 212.58.244.68: bytes=32 time=11ms TTL=54
Reply from 212.58.244.68: bytes=32 time=8ms TTL=54
Reply from 212.58.244.68: bytes=32 time=11ms TTL=54
Reply from 212.58.244.68: bytes=32 time=10ms TTL=54
Reply from 212.58.244.68: bytes=32 time=12ms TTL=54
Reply from 212.58.244.68: bytes=32 time=7ms TTL=54

Ping statistics for 212.58.244.68:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 12ms, Average = 9ms

The question is pointless as are any answers that will be given.

thanks again

P.S. a piece of string is twice the distance from the middle to either end (hehe sorry i couldnt resist it)

thanks for the insight into the P2P throttling, and its OK after midnight and right up until 5pm when its supposed to start? because ive heard otherwise?

cheers

On cable you can see huge differences between areas. Each area comprises a few hundred modems. For example I could be doing fine but somebody a couple of streets away could be getting poor service. A lot of the gripes you'll see about STM and shaping are possibly simply congestion problems which VM will not fix or they'd have to drop the "unlimited" tag from their advertising.

In reply to a post by paulb100:

thanks again

P.S. a piece of string is twice the distance from the middle to either end (hehe sorry i couldnt resist it)

thanks for the insight into the P2P throttling, and its OK after midnight and right up until 5pm when its supposed to start? because ive heard otherwise?

cheers

No - unless they've changed something or there's been a software upgrade if it's the same downloads it'll stay throttled as it's already been tagged. Once downloads are started again they'll be fine.

The stuff that does the throttling only looks closely at enough packets to establish what each connection is, once it has done that it carries out the tagging action on P2P / Usenet. It continues to do this for the duration on that connection.