Menu
What's new
By:
Filters Better Search

Simple test request on R7800

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

O

Odkrys

Senior Member
Hi.
Can someone please run the following test on R7800 5Ghz?

It would be nice if it was a Windows laptop.

2 cmds, one for ping and another for iperf.
iperf -s on R7800.

ping 192.168.x.1 -t

iperf -c 192.168.x.1 (router) -w 1M -P 5
and then,
iperf -c 192.168.x.1 (router) -w 64k -P 5

I am curious about the throughput and latency of the qualcomm wireless chipset.
 
iPerf 3 from a Samsung phone, Wifi 5GHz @ 433 Mbps.
Command from phone: iperf3 -c 192.158.0.1 -P 5
Code: 
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.0.3, port 37708
[  5] local 192.168.0.1 port 5201 connected to 192.168.0.3 port 37710
[  8] local 192.168.0.1 port 5201 connected to 192.168.0.3 port 37712
[ 10] local 192.168.0.1 port 5201 connected to 192.168.0.3 port 37714
[ 12] local 192.168.0.1 port 5201 connected to 192.168.0.3 port 37716
[ 14] local 192.168.0.1 port 5201 connected to 192.168.0.3 port 37718
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.26  sec  54.9 MBytes  44.9 Mbits/sec                  
[  8]   0.00-10.26  sec  55.2 MBytes  45.1 Mbits/sec                  
[ 10]   0.00-10.26  sec  54.1 MBytes  44.2 Mbits/sec                  
[ 12]   0.00-10.26  sec  57.1 MBytes  46.7 Mbits/sec                  
[ 14]   0.00-10.26  sec  54.4 MBytes  44.5 Mbits/sec                  
[SUM]   0.00-10.26  sec   276 MBytes   225 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.26  sec  54.9 MBytes  44.9 Mbits/sec                  receiver
[  8]   0.00-10.26  sec  55.2 MBytes  45.1 Mbits/sec                  receiver
[ 10]   0.00-10.26  sec  54.1 MBytes  44.2 Mbits/sec                  receiver
[ 12]   0.00-10.26  sec  57.1 MBytes  46.7 Mbits/sec                  receiver
[ 14]   0.00-10.26  sec  54.4 MBytes  44.5 Mbits/sec                  receiver
[SUM]   0.00-10.26  sec   276 MBytes   225 Mbits/sec                  receiver
 
HELLO_wORLD said:
Command from phone: iperf3 -c 192.158.0.1 -P 5
Click to expand...
Thanks. But i need the result of ping test.
I am seeing a significant increase in latency in tcp concurrent situation on asus rt-ac86u.

This is not a problem for small windows sizes, but seems to be a significant problem for typical window sizes.

In a fast bandwidth (my 500mbps internet, this is close to the throughput limit of 5Ghz 866mbps), it looks pretty bad when I need simultaneous tcp connection.

iperf -c 192.168.50.1 -w 1M -P 5
Code: 
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=41ms TTL=64
Reply from 192.168.50.1: bytes=32 time=81ms TTL=64
Reply from 192.168.50.1: bytes=32 time=79ms TTL=64
Reply from 192.168.50.1: bytes=32 time=82ms TTL=64
Reply from 192.168.50.1: bytes=32 time=73ms TTL=64
Reply from 192.168.50.1: bytes=32 time=77ms TTL=64
Reply from 192.168.50.1: bytes=32 time=78ms TTL=64
Reply from 192.168.50.1: bytes=32 time=82ms TTL=64
Reply from 192.168.50.1: bytes=32 time=77ms TTL=64
Reply from 192.168.50.1: bytes=32 time=72ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64

iperf -c 192.168.50.1 -w 64k -P 5
Code: 
Reply from 192.168.50.1: bytes=32 time=2ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=17ms TTL=64
Reply from 192.168.50.1: bytes=32 time=10ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=11ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=10ms TTL=64
Reply from 192.168.50.1: bytes=32 time=7ms TTL=64
Reply from 192.168.50.1: bytes=32 time=5ms TTL=64
Reply from 192.168.50.1: bytes=32 time=11ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
Reply from 192.168.50.1: bytes=32 time=6ms TTL=64
Reply from 192.168.50.1: bytes=32 time=1ms TTL=64
 
I don’t think I can make an accurate test for you.
Here are my pings to iPad, then phone, both on 5GHz, but without iPerf running :
Code: 
root@HERMES:~$ ping 192.168.0.6
PING 192.168.0.6 (192.168.0.6): 56 data bytes
64 bytes from 192.168.0.6: seq=0 ttl=64 time=2.249 ms
64 bytes from 192.168.0.6: seq=1 ttl=64 time=3.187 ms
64 bytes from 192.168.0.6: seq=2 ttl=64 time=105.592 ms
64 bytes from 192.168.0.6: seq=3 ttl=64 time=3.343 ms
64 bytes from 192.168.0.6: seq=4 ttl=64 time=80.537 ms
64 bytes from 192.168.0.6: seq=5 ttl=64 time=103.843 ms
64 bytes from 192.168.0.6: seq=6 ttl=64 time=26.336 ms
64 bytes from 192.168.0.6: seq=7 ttl=64 time=49.422 ms
64 bytes from 192.168.0.6: seq=8 ttl=64 time=74.008 ms
64 bytes from 192.168.0.6: seq=9 ttl=64 time=96.939 ms
64 bytes from 192.168.0.6: seq=10 ttl=64 time=18.932 ms
64 bytes from 192.168.0.6: seq=11 ttl=64 time=43.174 ms
64 bytes from 192.168.0.6: seq=12 ttl=64 time=4.030 ms
64 bytes from 192.168.0.6: seq=13 ttl=64 time=21.712 ms
64 bytes from 192.168.0.6: seq=14 ttl=64 time=12.215 ms
64 bytes from 192.168.0.6: seq=15 ttl=64 time=35.333 ms
64 bytes from 192.168.0.6: seq=16 ttl=64 time=59.544 ms
^C
--- 192.168.0.6 ping statistics ---
17 packets transmitted, 17 packets received, 0% packet loss
round-trip min/avg/max = 2.249/43.552/105.592 ms
root@HERMES:~$ ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: seq=0 ttl=64 time=5.436 ms
64 bytes from 192.168.0.3: seq=1 ttl=64 time=5.311 ms
64 bytes from 192.168.0.3: seq=2 ttl=64 time=35.145 ms
64 bytes from 192.168.0.3: seq=3 ttl=64 time=58.701 ms
64 bytes from 192.168.0.3: seq=4 ttl=64 time=2.343 ms
64 bytes from 192.168.0.3: seq=5 ttl=64 time=107.810 ms
64 bytes from 192.168.0.3: seq=6 ttl=64 time=26.929 ms
64 bytes from 192.168.0.3: seq=7 ttl=64 time=52.952 ms
64 bytes from 192.168.0.3: seq=8 ttl=64 time=75.195 ms
64 bytes from 192.168.0.3: seq=9 ttl=64 time=102.031 ms
64 bytes from 192.168.0.3: seq=10 ttl=64 time=21.899 ms
64 bytes from 192.168.0.3: seq=11 ttl=64 time=45.173 ms
64 bytes from 192.168.0.3: seq=12 ttl=64 time=68.916 ms
^C
--- 192.168.0.3 ping statistics ---
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max = 2.343/46.757/107.810 ms
I guess tablets and phones are not good for these tests.
 
On Windows laptop:

iperf3.exe -s

on R7800 (AP mode):

Code: 
root@ap2:~$ iperf3 -c 192.168.200.203 -P 5 -R
Connecting to host 192.168.200.203, port 5201
Reverse mode, remote host 192.168.200.203 is sending
[  5] local 192.168.200.3 port 40518 connected to 192.168.200.203 port 5201
[  7] local 192.168.200.3 port 40519 connected to 192.168.200.203 port 5201
[  9] local 192.168.200.3 port 40520 connected to 192.168.200.203 port 5201
[ 11] local 192.168.200.3 port 40521 connected to 192.168.200.203 port 5201
[ 13] local 192.168.200.3 port 40522 connected to 192.168.200.203 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  16.4 MBytes   137 Mbits/sec
[  7]   0.00-1.00   sec  11.5 MBytes  96.7 Mbits/sec
[  9]   0.00-1.00   sec  9.69 MBytes  81.3 Mbits/sec
[ 11]   0.00-1.00   sec  10.0 MBytes  83.9 Mbits/sec
[ 13]   0.00-1.00   sec  9.63 MBytes  80.7 Mbits/sec
[SUM]   0.00-1.00   sec  57.2 MBytes   480 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   1.00-2.00   sec  17.0 MBytes   143 Mbits/sec
[  7]   1.00-2.00   sec  13.7 MBytes   115 Mbits/sec
[  9]   1.00-2.00   sec  9.31 MBytes  78.1 Mbits/sec
[ 11]   1.00-2.00   sec  9.25 MBytes  77.6 Mbits/sec
[ 13]   1.00-2.00   sec  9.34 MBytes  78.4 Mbits/sec
[SUM]   1.00-2.00   sec  58.6 MBytes   491 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  15.1 MBytes   127 Mbits/sec
[  7]   2.00-3.00   sec  12.7 MBytes   107 Mbits/sec
[  9]   2.00-3.00   sec  10.6 MBytes  88.6 Mbits/sec
[ 11]   2.00-3.00   sec  7.50 MBytes  62.9 Mbits/sec
[ 13]   2.00-3.00   sec  9.24 MBytes  77.5 Mbits/sec
[SUM]   2.00-3.00   sec  55.2 MBytes   463 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  12.8 MBytes   107 Mbits/sec
[  7]   3.00-4.00   sec  10.6 MBytes  88.5 Mbits/sec
[  9]   3.00-4.00   sec  10.9 MBytes  91.3 Mbits/sec
[ 11]   3.00-4.00   sec  9.53 MBytes  79.9 Mbits/sec
[ 13]   3.00-4.00   sec  10.1 MBytes  84.8 Mbits/sec
[SUM]   3.00-4.00   sec  53.8 MBytes   452 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-5.00   sec  11.6 MBytes  97.6 Mbits/sec
[  7]   4.00-5.00   sec  9.65 MBytes  80.9 Mbits/sec
[  9]   4.00-5.00   sec  10.6 MBytes  88.9 Mbits/sec
[ 11]   4.00-5.00   sec  9.30 MBytes  78.0 Mbits/sec
[ 13]   4.00-5.00   sec  10.2 MBytes  85.6 Mbits/sec
[SUM]   4.00-5.00   sec  51.4 MBytes   431 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   5.00-6.00   sec  11.9 MBytes  99.7 Mbits/sec
[  7]   5.00-6.00   sec  10.9 MBytes  91.8 Mbits/sec
[  9]   5.00-6.00   sec  11.7 MBytes  98.2 Mbits/sec
[ 11]   5.00-6.00   sec  10.1 MBytes  84.6 Mbits/sec
[ 13]   5.00-6.00   sec  11.3 MBytes  94.4 Mbits/sec
[SUM]   5.00-6.00   sec  55.9 MBytes   469 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   6.00-7.00   sec  9.61 MBytes  80.6 Mbits/sec
[  7]   6.00-7.00   sec  10.4 MBytes  86.9 Mbits/sec
[  9]   6.00-7.00   sec  11.3 MBytes  94.6 Mbits/sec
[ 11]   6.00-7.00   sec  10.1 MBytes  84.8 Mbits/sec
[ 13]   6.00-7.00   sec  10.8 MBytes  90.9 Mbits/sec
[SUM]   6.00-7.00   sec  52.2 MBytes   438 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   7.00-8.00   sec  9.69 MBytes  81.3 Mbits/sec
[  7]   7.00-8.00   sec  10.2 MBytes  85.5 Mbits/sec
[  9]   7.00-8.00   sec  11.3 MBytes  94.8 Mbits/sec
[ 11]   7.00-8.00   sec  11.4 MBytes  95.9 Mbits/sec
[ 13]   7.00-8.00   sec  10.9 MBytes  91.3 Mbits/sec
[SUM]   7.00-8.00   sec  53.5 MBytes   449 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   8.00-9.00   sec  10.3 MBytes  86.4 Mbits/sec
[  7]   8.00-9.00   sec  9.80 MBytes  82.2 Mbits/sec
[  9]   8.00-9.00   sec  10.9 MBytes  91.4 Mbits/sec
[ 11]   8.00-9.00   sec  11.2 MBytes  93.7 Mbits/sec
[ 13]   8.00-9.00   sec  10.5 MBytes  87.7 Mbits/sec
[SUM]   8.00-9.00   sec  52.6 MBytes   441 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   9.00-10.00  sec  10.6 MBytes  88.8 Mbits/sec
[  7]   9.00-10.00  sec  9.69 MBytes  81.3 Mbits/sec
[  9]   9.00-10.00  sec  10.5 MBytes  88.3 Mbits/sec
[ 11]   9.00-10.00  sec  10.6 MBytes  89.2 Mbits/sec
[ 13]   9.00-10.00  sec  10.3 MBytes  86.4 Mbits/sec
[SUM]   9.00-10.00  sec  51.7 MBytes   434 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.03  sec   126 MBytes   105 Mbits/sec                  sender
[  5]   0.00-10.00  sec   125 MBytes   105 Mbits/sec                  receiver
[  7]   0.00-10.03  sec   110 MBytes  92.0 Mbits/sec                  sender
[  7]   0.00-10.00  sec   109 MBytes  91.5 Mbits/sec                  receiver
[  9]   0.00-10.03  sec   108 MBytes  90.1 Mbits/sec                  sender
[  9]   0.00-10.00  sec   107 MBytes  89.5 Mbits/sec                  receiver
[ 11]   0.00-10.03  sec   100 MBytes  83.6 Mbits/sec                  sender
[ 11]   0.00-10.00  sec  99.0 MBytes  83.0 Mbits/sec                  receiver
[ 13]   0.00-10.03  sec   103 MBytes  86.3 Mbits/sec                  sender
[ 13]   0.00-10.00  sec   102 MBytes  85.8 Mbits/sec                  receiver
[SUM]   0.00-10.03  sec   547 MBytes   457 Mbits/sec                  sender
[SUM]   0.00-10.00  sec   542 MBytes   455 Mbits/sec                  receiver

iperf Done.

Ping from Windows laptop to R7800 (iperf3 is running):

ping -n 20 192.168.200.2
Code: 
Pinging 192.168.200.2 with 32 bytes of data:
Reply from 192.168.200.2: bytes=32 time=60ms TTL=64
Reply from 192.168.200.2: bytes=32 time=40ms TTL=64
Reply from 192.168.200.2: bytes=32 time=77ms TTL=64
Reply from 192.168.200.2: bytes=32 time=83ms TTL=64
Reply from 192.168.200.2: bytes=32 time=69ms TTL=64
Reply from 192.168.200.2: bytes=32 time=83ms TTL=64
Reply from 192.168.200.2: bytes=32 time=108ms TTL=64
Reply from 192.168.200.2: bytes=32 time=112ms TTL=64
Reply from 192.168.200.2: bytes=32 time=73ms TTL=64
Reply from 192.168.200.2: bytes=32 time=83ms TTL=64
Reply from 192.168.200.2: bytes=32 time=6ms TTL=64
Reply from 192.168.200.2: bytes=32 time=6ms TTL=64
Reply from 192.168.200.2: bytes=32 time=6ms TTL=64
Reply from 192.168.200.2: bytes=32 time=5ms TTL=64
Reply from 192.168.200.2: bytes=32 time=6ms TTL=64
Reply from 192.168.200.2: bytes=32 time=5ms TTL=64
Reply from 192.168.200.2: bytes=32 time=5ms TTL=64
Reply from 192.168.200.2: bytes=32 time=5ms TTL=64
Reply from 192.168.200.2: bytes=32 time=8ms TTL=64
Reply from 192.168.200.2: bytes=32 time=6ms TTL=64

Connection: 5GHz.

Voxel.
 
Last edited:
You must log in or register to reply here.

Similar threads

D
Entware Voxel FW reverse proxy help
Replies
2
Views
467
Duke_
D
cyruz
Simple script for DNS fallback
Replies
8
Views
707
cyruz
cyruz
W
Mystery of connection speed in Netflix app in TV - with or without network switch
Replies
14
Views
1K
follower
F
R
One router, two segments desired.
Replies
4
Views
384
Rombo
R
S
Mac OS SMB max NVME throughput on 10GbE network?
Replies
4
Views
1K
Tech Junky
T

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 867 (members: 14, guests: 853)
Top