![]() ![]() ![]() |
|
RayZhou:
Linux:
We can't see a problem and your link is broken
John
can you see it now?
Yes kind of it's way too small
John
Linux:
RayZhou:
Linux:
We can't see a problem and your link is broken
John
can you see it now?
Yes kind of it's way too small
John
'Open image in new tab' makes it readable
RayZhou:
Thanks for all of your helpful answer. I got much better understanding for the issue.
By using other tool PingPlotter as suggested, i may find where is problem
see screenshot. 50% packet loss may is problem
Right, okay so this is World of tanks.
that latency is somewhat to be expected. as discussed above, routing to SG is particularly iffy latency wise.
this will heavily depend on what the current state of undersea cables are, and the decisions made further upstream from the provider about what routes to take.
GGI routes are sometimes not the lowest latency, but Quite typically very consistent and has solid bandwidth.
Overall depending on route the lowest you would get is about 130ish, that would be over the amentioned SEA-ME-3 which is often not working.
the alternative routes at best land 180ish from auckland. so 200 from Dunedin, that's not bad.
Realistically, your still over that 100+ mark, so the next really noticeable mark is about 250ms on average where "lag" is preserved to be increasingly bad.
Overal, it's packetloss and jitter that will hurt more than a slightly higher base latency.
I have multiple connections at home, One is spark, the other is Vodafone.
In my personal experience in gaming, the two have minor differances in routes, one beats another at certain cases but nothing overall. Where i really do notice it though, is the Vodafone connection can experience a fair bit more jitter. Spark on the other hand is pretty rock solid so i don't feel any sort of rubberyness.
Don't look at latency as a target, Physics can't always be beaten in the snap of fingers.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Thanks for your explanation.
I am expecting the high pings than other part of world. I just need to find the where is lagging come from.
So 50% of packet loss is what i am looking for. next thing for me is go to find how to avoid it. i may need to adjust some setting in the router.
thank you again.
Move to Singapore
John
RayZhou:
Thanks for your explanation.
I am expecting the high pings than other part of world. I just need to find the where is lagging come from.
So 50% of packet loss is what i am looking for. next thing for me is go to find how to avoid it. i may need to adjust some setting in the router.
thank you again.
That 50% your seeing on that pingplotter is intended.
You aren't actually seeing packetloss, What this is is deprioritization on ICMP on that node.
This is a standard network configuration and you will see it around many places, not isolated to Spark.
If you truly were seeing 50% of packets dropping on that hop, all other hops past it would also see the same loss.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Also, and average of 4ms to your local router?
Is your machine on wifi?
Edit: Sorry just realised that's an iPad. Why test from an iPad?!?!?
RayZhou:
Thanks for all of your helpful answer. I got much better understanding for the issue.
By using other tool PingPlotter as suggested, i may find where is problem
see screenshot. 50% packet loss may is problem
As explained above your interpretation of how traceroute and MTR are not correct.
Your image shows no packet loss to end end destination and no issue.
It does show ICMP depriorisiation on a single router which is 50% packet loss on ICMP traffic to that single router. This does not affect your traffic.
RayZhou:
Thanks for your explanation.
I am expecting the high pings than other part of world. I just need to find the where is lagging come from.
So 50% of packet loss is what i am looking for. next thing for me is go to find how to avoid it. i may need to adjust some setting in the router.
thank you again.
The 50% loss you are seeing is expected and normal. It's only ICMP, it's only on that hop and not on anything further upstream. It's an artefact and means NOTHING.
There is nothing you need to adjust in the router.
As per other replies to fix this you can play on different servers or move to Singapore/Hong Kong I'm afraid.
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
sbiddle:
RayZhou:
Thanks for all of your helpful answer. I got much better understanding for the issue.
By using other tool PingPlotter as suggested, i may find where is problem
see screenshot. 50% packet loss may is problem
As explained above your interpretation of how traceroute and MTR are not correct.
Your image shows no packet loss to end end destination and no issue.
It does show ICMP depriorisiation on a single router which is 50% packet loss on ICMP traffic to that single router. This does not affect your traffic.
Do note that was done on an iPad with WiFi...
Kraven:
Assumptions being made here, but the IP address in the OP matches the *old* World Of Tanks SG server address so safe to assume this is about ping to World Of Tanks.
Wargaming moved the server from SG to HK a while back so SEA-ME-3 is no longer an issue. Also AUS/NZ players should be using the AUS server now if they are concerned about ping - but lack of players there makes the queue times suck.
80 or 90 players on the AUS/NZ server at quiet times. Playing a medium or heavy will often not be too bad a wait, but the wait times for arty (favourite) are so bad that I switch over to the HK server. Also, ping doesn't make as much of a difference for arty...
|
![]() ![]() ![]() |