New Data Center "greater Latency Performance To Many Our Non Na Customers"?
#41
Posted 29 August 2014 - 10:41 PM
#42
Posted 29 August 2014 - 10:42 PM
Edited by NextGame, 29 August 2014 - 10:43 PM.
#43
Posted 29 August 2014 - 10:45 PM
Besides, they couldn't get any more servers in the Piranha Kitchen, and the cooling from leaving the refrigerator door open was becoming less effective..
#44
Posted 29 August 2014 - 10:46 PM
#45
Posted 29 August 2014 - 10:52 PM
I'll include a link so it looks like I might know what I'm talking about.
http://www2.publicat...C_11/C11_A.html
Unfortunately, I think my American English translator is erroneously pulling from the profanity filter database, because I keep seeing it spammed across my screen in every match.
Anyway, yeah, lag.
#46
Posted 29 August 2014 - 11:29 PM
#47
Posted 29 August 2014 - 11:40 PM
#48
Posted 30 August 2014 - 12:07 AM
#49
Posted 30 August 2014 - 12:22 AM
#50
Posted 30 August 2014 - 12:31 AM
#51
Posted 30 August 2014 - 12:51 AM
#52
Posted 30 August 2014 - 12:54 AM
Training Instructor, on 29 August 2014 - 10:22 PM, said:
Just my two cents.
From what I heard last.. WTFast does not work with MWO. Until it is listed as compatibile.. Don't go further than the free trial to test it. You can get it to launcher but the wtfast proxy cannot get into the mwo ingame. Just crashes back to mechlab, last I tried.
--
Latency is better for me from Singapore. Down from 250ms++ with a lot of jitter to 231ms+ with little jitter.
You guys can ping the MWO game srever since they moved from Internap to OVH Datacenter in Montreal.
IP address is 192.99.40.106.
Quote
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| xxxxxxxxxxxxxxxxxxxxx - 0 | 689 | 689 | 0 | 0 | 71 | 0 |
| No response from host - 100 | 138 | 0 | 0 | 0 | 0 | 0 |
| 242.246.65.202.unknown.m1.com.sg - 0 | 689 | 689 | 3 | 5 | 100 | 4 |
| 241.246.65.202.unknown.m1.com.sg - 0 | 689 | 689 | 1 | 5 | 89 | 2 |
| 37.246.65.202.unknown.m1.com.sg - 0 | 689 | 689 | 1 | 5 | 97 | 3 |
| 21.246.65.202.unknown.m1.com.sg - 0 | 689 | 689 | 2 | 6 | 79 | 3 |
| any2ix.coresite.com - 17 | 419 | 351 | 162 | 218 | 438 | 162 |
| 198.27.73.165 - 94 | 145 | 9 | 0 | 223 | 225 | 223 |
| bhs-g2-6k.qc.ca - 0 | 689 | 689 | 231 | 232 | 253 | 232 |
| bhs-s4-6k.qc.ca - 1 | 685 | 684 | 230 | 233 | 458 | 231 |
| ns7000227.ip-192-99-40.net - 0 | 689 | 689 | 230 | 231 | 234 | 231 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Edited by ShinVector, 30 August 2014 - 01:26 AM.
#53
Posted 30 August 2014 - 01:22 AM
Our last government didnt do a very good job rolling out the fibre optic network before they got booted by the current government and they are not doing much better. Most people are still on the old copper network.
Seriously look at this map and go zoom in on any capital city and see how random it is. http://www.nbnco.com...ollout-map.html
#54
Posted 30 August 2014 - 01:33 AM
I can fling my finger at PGI for a lot of reasons but this isn't one of them. Frankly I am impressed what they have been able to do with one server.
#55
Posted 30 August 2014 - 01:46 AM
Quote
* Unknown Host * 192.168.1.1 1 0ms 0ms 0% 31 / 31
* Unknown Host * 172.18.17.181 3 23ms 25ms 0% 31 / 31
* Unknown Host * 172.18.16.101 4 29ms 29ms 0% 31 / 31
* Unknown Host * 172.19.241.21 5 46ms 46ms 0% 30 / 30
bundle-ether11.milano50.mil.seabone.net 93.186.128.229 6 43ms 39ms 0% 30 / 30
xe-2-0-3.milano51.mil.seabone.net 195.22.205.109 7 34ms 35ms 0% 30 / 30
mil-1-6k.it.eu 213.186.32.213 8 50ms 39ms 0% 30 / 30
fra-5-6k.fr.eu 91.121.128.35 10 42ms 53ms 0% 30 / 30
rbx-g2-a9.fr.eu 91.121.131.201 11 51ms 51ms 0% 30 / 30
* Unknown Host * 0.0.0.0 12 0ms
nwk-2-6k.nj.us 178.32.135.230 13 154ms 157ms 0% 30 / 30
bhs-g2-6k.qc.ca 198.27.73.207 14 164ms 164ms 0% 30 / 30
bhs-s3-6k.qc.ca 198.27.73.142 15 162ms 165ms 0% 30 / 30
ns7000227.ip-192-99-40.net 192.99.40.106 16 162ms 163ms 0% 30 / 30
Could be better but at least there is no packet loss apparently.
Edited by EvilCow, 30 August 2014 - 01:49 AM.
#56
Posted 30 August 2014 - 01:47 AM
ShinVector, on 30 August 2014 - 12:54 AM, said:
From what I heard last.. WTFast does not work with MWO. Until it is listed as compatibile.. Don't go further than the free trial to test it. You can get it to launcher but the wtfast proxy cannot get into the mwo ingame. Just crashes back to mechlab, last I tried.
--
Latency is better for me from Singapore. Down from 250ms++ with a lot of jitter to 231ms+ with little jitter.
You guys can ping the MWO game srever since they moved from Internap to OVH Datacenter in Montreal.
IP address is 192.99.40.106.
Ok, did a trace and I have route 15,16,17 that add about 75 ping which are not showing on your trace.
Is this a time of day and Aussies are playing on the Off-Peak service?
Anyway, below is a cut of the trace
Edited by Night Fury76, 30 August 2014 - 01:50 AM.
#57
Posted 30 August 2014 - 01:48 AM
Edited by Monkey Lover, 30 August 2014 - 01:57 AM.
#58
Posted 30 August 2014 - 02:16 AM
Night Fury76, on 30 August 2014 - 01:47 AM, said:
Ok, did a trace and I have route 15,16,17 that add about 75 ping which are not showing on your trace.
Is this a time of day and Aussies are playing on the Off-Peak service?
Anyway, below is a cut of the trace
We using different ISPs.. heck different Countries.
It boils down to your the uplinks your ISP and it 'seems' Telstra is not a very good path to reach the new MWO game servers. *or this path is congested.
Not sure about the reverse router though.
Monkey Lover, on 30 August 2014 - 01:48 AM, said:
Yeah.. DEsync issue still there.. Though not too much for me.
Edited by ShinVector, 30 August 2014 - 02:28 AM.
#59
Posted 30 August 2014 - 02:37 AM
Anyway, someone said they moved from toronto to montreal, there's no way a move like that should increase ping by ~70ms, probably something going wrong with routing, up to the isp to fix it.
a year ago my isp had some big trouble routing this game as well, had ping going from 150 to 230 all the time, causing rubberbanding and crosshair adjustments, very annoying, but I guess they fixed it.
#60
Posted 30 August 2014 - 02:41 AM
Running light mechs is an issue though - much rubberbanding especially when running into another mech. The system takes about 1 second to realise you really shouldn't be on the other side of the mech and then you bounce back and forth for a while before ended up where you should be...
Cheers!
Eboli
13 user(s) are reading this topic
0 members, 13 guests, 0 anonymous users