New 2011 MBP bad ping times

[Robbug]

No you're not being rude. 🙂 You bring up valid points. I have been noticing serious performance issues with MMO's. What I find is under OS X network performance has this tendency to take a nose dive. Under Win 7 it appears those issues are non existent.

You're right - I failed at search fu - will revive that thread and kill this one.

 

[Nermal]

You're right - I failed at search fu - will revive that thread and kill this one.

If it wasn't for this thread then I wouldn't have even known about the problem so in a way I'm glad 🙂

Nevertheless, I'll merge the threads so that all the information is in one place.

 

[enklined]

No you're not being rude. 🙂 You bring up valid points. I have been noticing serious performance issues with MMO's. What I find is under OS X network performance has this tendency to take a nose dive. Under Win 7 it appears those issues are non existent.

You're right - I failed at search fu - will revive that thread and kill this one.

I'm enklined to think OSX does this intentionally. Has was eluded to in this thread, it's probably done to increase battery life.

Honestly I think it's a non-issue. I doubt this would be the reason you/anyone would get lag during gameplay.

 

[Robbug]

Thanks for the thread merge! As to the ping times etc -

As stated above and throughout, ping times do steady out after an initial "kick start" to the wireless...but - when playing MMO's - the games appear to try to minimize how much data is being sent to and from the server. So if there isn't much needed to be sent to and from, the mac wireless adapter will go into reduced power mode until the next request is sent from the client. Unfortunately this adversely affects the playability of MMOs. (i.e lag spikes or jerkyness)

FPSs probably are not affected since the client constantly will update location, health and other data. MMO's don't necessarily have to always do that under certain circumstances- thinkin low population areas etc.

Again I am theorycrafting here but the evidence does lead to a cause and effect relationship.

Under normal wireless transfers, this would not really affect anything. When using a client to server type game which constant data streaming would bring the main servers down to its knees, it appears there becomes a conflict.

Thoughts?

Edit:

I'm enklined to think OSX does this intentionally. Has was eluded to in this thread, it's probably done to increase battery life.

Honestly I think it's a non-issue. I doubt this would be the reason you/anyone would get lag during gameplay.

Fair enough - thats why I am asking if there are others that may be in my situation that may be experiencing this. If not I will look again to my local setups etc. It's just really night and day under two different OSs for me.

 

[Nermal]

Honestly I think it's a non-issue. I doubt this would be the reason you/anyone would get lag during gameplay.

Yet that seems to be the case. As soon as I switch from Wi-Fi to Ethernet, my WoW latency goes from yellow (laggy) to green (good). With my old 2006 MBP it sat on green regardless of which interface I was using.

 

[sau]

After installing the MacBook Pro Software Update 1.4 and EFI Update 2.1 my ping times are much lower and consistant while the network usage is at idle. Maybe Apple slipped in a fix for it without mentioning it.

PING 192.168.7.1 (192.168.7.1): 56 data bytes
64 bytes from 192.168.7.1: icmp_seq=0 ttl=64 time=1.448 ms
64 bytes from 192.168.7.1: icmp_seq=1 ttl=64 time=3.582 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=64 time=0.960 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=64 time=1.768 ms
64 bytes from 192.168.7.1: icmp_seq=4 ttl=64 time=1.182 ms
64 bytes from 192.168.7.1: icmp_seq=5 ttl=64 time=4.385 ms
64 bytes from 192.168.7.1: icmp_seq=6 ttl=64 time=1.004 ms
64 bytes from 192.168.7.1: icmp_seq=7 ttl=64 time=3.438 ms
64 bytes from 192.168.7.1: icmp_seq=8 ttl=64 time=2.560 ms
64 bytes from 192.168.7.1: icmp_seq=9 ttl=64 time=3.479 ms
64 bytes from 192.168.7.1: icmp_seq=10 ttl=64 time=1.445 ms
64 bytes from 192.168.7.1: icmp_seq=11 ttl=64 time=3.422 ms
64 bytes from 192.168.7.1: icmp_seq=12 ttl=64 time=1.145 ms
64 bytes from 192.168.7.1: icmp_seq=13 ttl=64 time=1.220 ms
64 bytes from 192.168.7.1: icmp_seq=14 ttl=64 time=1.240 ms
64 bytes from 192.168.7.1: icmp_seq=15 ttl=64 time=1.763 ms
^C
--- 192.168.7.1 ping statistics ---
16 packets transmitted, 16 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.960/2.128/4.385/1.115 ms

This is while at work, my previous posts in this thread include tests from both work and home, both of which were bad before.