Thread: 30M Finally had enough of VM BS...........
View Single Post
Old 05-09-2012, 23:09   #81
qasdfdsaq
cf.mega poster
 
Join Date: Aug 2004
Posts: 11,207
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
Re: Finally had enough of VM BS...........
Quote:
Originally Posted by kwikbreaks View Post
Yes cable can deliver but for many it simply doesn't. Mines fine right now but it has been poor in the past.
Indeed, pinging some Austrian guy's 15/1 cable connection today (from my BT line mind you, so it has the jitter of both our connections added together):

RTTs of replies in ms: min/avg/max/dev: 56.109 / 56.982 / 60.922 / 1.511

Spoiler: 
Pinging 90.146.212.178 with 32 bytes of data:
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=55ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=55ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=57ms TTL=47
Reply from 90.146.212.178: bytes=32 time=56ms TTL=47
Reply from 90.146.212.178: bytes=32 time=55ms TTL=47
Reply from 90.146.212.178: bytes=32 time=58ms TTL=47
Reply from 90.146.212.178: bytes=32 time=58ms TTL=47

Ping statistics for 90.146.212.178:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 58ms, Average = 56ms


Meanwhile in VM land (this is VM 100Mb EH9 on my ping page, so reasonably good for VM):

RTTs of replies in ms: min/avg/max/dev: 38.945 / 44.493 / 58.957 / 4.376

Spoiler: 
Pinging d1.qasdfdsaq.com [92.235.190.31] with 32 bytes of data:
Reply from 92.235.190.31: bytes=32 time=54ms TTL=47
Reply from 92.235.190.31: bytes=32 time=44ms TTL=47
Reply from 92.235.190.31: bytes=32 time=39ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=43ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=39ms TTL=47
Reply from 92.235.190.31: bytes=32 time=47ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=45ms TTL=47
Reply from 92.235.190.31: bytes=32 time=40ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=41ms TTL=47
Reply from 92.235.190.31: bytes=32 time=42ms TTL=47
Reply from 92.235.190.31: bytes=32 time=51ms TTL=47
Reply from 92.235.190.31: bytes=32 time=50ms TTL=47
Reply from 92.235.190.31: bytes=32 time=48ms TTL=47
Reply from 92.235.190.31: bytes=32 time=40ms TTL=47

Ping statistics for 92.235.190.31:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 54ms, Average = 43ms


Meanwhile in BT land...

RTTs of replies in ms: min/avg/max/dev: 21.395 / 21.635 / 21.756 / 0.103

Spoiler: 
Pinging bbc.qasdfdsaq.com [212.58.246.94] with 32 bytes of data:
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51
Reply from 212.58.246.94: bytes=32 time=21ms TTL=51

Ping statistics for 212.58.246.94:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 21ms, Average = 21ms
qasdfdsaq is offline