Is this 5Ghz WiFi performance good?

[Barry~~]

Just for curious, is these data shown of WiFi Good for gaming?

32 Bytes of data:

Ping 192.168.0.1 (Using 32 Bytes of data):
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64
Return from 192.168.0.1: Bytes=32 Time<1ms TTL=64

192.168.0.1 的 Ping Stats Data:
    Packets: Sent = 24，Received = 24, Lost = 0 (0% Lost)，
Average Time (miliseconds):
    Minimum = 0ms，Maximum = 2ms，Avg. = 0ms
Control-C

10000 Bytes of data

Ping 192.168.0.1 (Used 10000 Bytesof data):
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=5ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=8ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=86ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=2ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=7ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=8ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=4ms TTL=64
Return from 192.168.0.1: Bytes=10000 Time=3ms TTL=64

192.168.0.1 的 Ping Static:
    Packets: Sent = 35，Received = 35, Lost = 0 (0% Lost)，
Average Time (Miliseconds):
    Minimum = 2ms，Maximum = 86ms，Average = 5ms
Control-C

65500 Bytes:

Ping 192.168.0.1 (Used 65500 Bytes的Data):
Return from 192.168.0.1: Bytes=65500 Time=15ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=42ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=28ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=16ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=19ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=37ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=54ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=51ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=17ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=30ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=19ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=33ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=14ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=15ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=13ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=13ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=21ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=10ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=46ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=16ms TTL=64
Return from 192.168.0.1: Bytes=65500 Time=11ms TTL=64

192.168.0.1 的 Ping 統計資料:
    Packets: Sent = 28，Recieved = 28, Lost = 0 (0% Lost)，
Average Time(Miliseconds):
    Minimum = 10ms，Maximum = 54ms，Average = 21ms
Control-C

Are these good?

Because I know that Ethernet will be <1 ms in anyways between Client and Server

 

BTW the wifi is over 40Mhz, channel 44 and its away like 3.5 metres.
 

[Denned]

It doesn't really tell you anything. You don't drop packages on those 20 pings, so I guess that's positive.

Your packages wont ever be 65500 or 10000 bytes, which is why it takes so much longer.

 

 

[Barry~~]

48 minutes ago, Denned said:

It doesn't really tell you anything. You don't drop packages on those 20 pings, so I guess that's positive.

Your packages wont ever be 65500 or 10000 bytes, which is why it takes so much longer.

 

 

YES, my another question.

 

How much Packets would a game running 64 tick server lick CS:GO take?

does TTL means how many packets? Damn thats a lot if one Packet of 65500 Bytes of data .

[mynameisjuan]

MTU standard is 1500 bytes. After that packets begin to fragment which chews up CPU and delay which them needs to be recombined on the relieving device.

 

This is why you are seeing higher latency and just know that device avoid fragmenting as much as possible and some devices are configured to drop fragmented packets.

[Denned]

2 hours ago, Barry~~ said:

YES, my another question.

 

How much Packets would a game running 64 tick server lick CS:GO take?

does TTL means how many packets? Damn thats a lot if one Packet of 65500 Bytes of data .

That's impossible to answer. Like 100000 depending on what time frame we are talking about. It would be better do to a speedtest. CSGO doesn't take up much bandwidth, so maybe like 500-1000 kbps.

TTL is time to live. That means every time the package hits a hop, a counter is increased by one. So a hop would be first your router, then maybe a point of presense of your ISP, then a bunch more from your isp. And if somehow it manages to hop more than 64 times, then it's dropped. Which should never happen. TTL Is just a method to make sure packages don't circulate around the network forever.

[Lurick]

4 minutes ago, Denned said:

That's impossible to answer. Like 100000 depending on what time frame we are talking about. It would be better do to a speedtest. CSGO doesn't take up much bandwidth, so maybe like 500-1000 kbps.

TTL is time to live. That means every time the package hits a hop, a counter is increased by one. So a hop would be first your router, then maybe a point of presense of your ISP, then a bunch more from your isp. And if somehow it manages to hop more than 64 times, then it's dropped. Which should never happen. TTL Is just a method to make sure packages don't circulate around the network forever.

You've got it backwards. TTL is decremented from. The lower the starting value the fewer number of hops the packet can take before it hits 0 and is discarded.

[Denned]

Just now, Lurick said:

You've got it backwards. TTL is decremented from. The lower the starting value the fewer number of hops the packet can take before it hits 0 and is discarded.

Yes right, mistyped

[Barry~~]

11 hours ago, Denned said:

That's impossible to answer. Like 100000 depending on what time frame we are talking about. It would be better do to a speedtest. CSGO doesn't take up much bandwidth, so maybe like 500-1000 kbps.

TTL is time to live. That means every time the package hits a hop, a counter is increased by one. So a hop would be first your router, then maybe a point of presense of your ISP, then a bunch more from your isp. And if somehow it manages to hop more than 64 times, then it's dropped. Which should never happen. TTL Is just a method to make sure packages don't circulate around the network forever.

Oh, understand a bit now...

but I am still confused in networking :P

BTW, 64 ticks is 64 packets / s?
And How will I test my latency between my router for 64 ticks?

because if it is gonna be below 5ms, I am not gonna buy a ethernet cable.

[Denned]

1 hour ago, Barry~~ said:

Oh, understand a bit now...

but I am still confused in networking

BTW, 64 ticks is 64 packets / s?
And How will I test my latency between my router for 64 ticks?

because if it is gonna be below 5ms, I am not gonna buy a ethernet cable.

64 tick is just 64 updates per second. An update could be any amount of packages. Basically the amount of trafic from that, is so little it doesn't mean anything for your network.

Gaming on WIFI shouldn't be a problem as such. The thing you might experience is interference from other networks, like it you live in an apartment complex.

There isn't much testing you can do, other than just trying it out and see how it feels.