View Single Post
Old 14-05-2012, 00:09   #2
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: Routing within the VM Network

I only see one graph (though when I did see two there was very little difference)

You can't get your routing changed. At least not easily, or individually. You could try forcing a change of IP, which might change routing. I've seen increases of 14ms on VM from the above.

Distance and latency have a funny weird interaction on VM's network. Birmingham to London takes longer than Manchester to London. A lot of VM traffic to Amsterdam also takes twice as long as it should, because it takes a shorter (!) path.

I don't think it's being picky - I get similarly peeved when BT do a MPLS reroute or turn interleaving on on my line (12-16ms extra latency) as I notice an immediate difference in gaming and remote desktop and VPN performance.

VM has made a serious turn towards cheap, fat, high latency pipes lately, at all levels of their network.
qasdfdsaq is offline   Reply With Quote