iptime 공유기 (AX2004T), 유선 핑 테스트 결과 (Ping Test)
테스트 장비
- 공유기#1 : Asus AC-68U
- 공유기#2 : iptime AX2004T
ㄴ https://prod.danawa.com/info/?pcode=95848220&keyword=ax2004t&cate=112804
- 노트북 : HP Victus, Realtek RTL8852AE WiFi6, Realtek Gaming GbE Family Controller
테스트 절차
* 정확한 값을 얻기 위해 파이썬 ping3 라이브러리를 활용함.
* 노트북(윈도우11) 에서 ping 을 대략 100회 정도 실시함.
* 노트북과 공유기는 장애물 없이 50cm 정도 떨어져 있음.
* 공유기#2(AX2004T)에는 노트북 외에 물려있는 장치는 없고, 테스트 중 다른 작업 하지 않음.
* 공유기#1(AC-68U)에는 원래 집에서 쓰던 각종 저부하 장치(WIFI) 그대로 연결되어 있음.
테스트 결과
테스트 | 경로 | 패킷 손실 | 응답속도(평균) | 응답속도(최소/최대) | 표준편차 |
1 | 노트북→유선→공유기#2 (AX2004T) | 0.0% | 1.469 ms | 0.807 / 13.924 ms | 1.763 ms |
2 | 노트북→유선→공유기#2→유선→공유기#1 | 0.0% | 1.932 ms | 1.152 / 17.853 ms | 2.219 ms |
3 | 노트북→유선→공유기#1 (AC-68U) | 0.0% | 1.095 ms | 0.903 / 2.730 ms | 0.205 ms |
DATA
# 테스트 1 : 노트북 ->유선->공유기#2(192.168.23.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.23.1 -n 100 Pinging 192.168.23.1 with 32 bytes of data: Reply from 192.168.23.1: seq=0 time=1.066ms Reply from 192.168.23.1: seq=1 time=0.963ms Reply from 192.168.23.1: seq=2 time=0.981ms Reply from 192.168.23.1: seq=3 time=0.917ms Reply from 192.168.23.1: seq=4 time=0.911ms Reply from 192.168.23.1: seq=5 time=0.958ms Reply from 192.168.23.1: seq=6 time=0.878ms Reply from 192.168.23.1: seq=7 time=1.043ms Reply from 192.168.23.1: seq=8 time=5.022ms Reply from 192.168.23.1: seq=9 time=0.973ms Reply from 192.168.23.1: seq=10 time=0.990ms Reply from 192.168.23.1: seq=11 time=1.108ms Reply from 192.168.23.1: seq=12 time=0.998ms Reply from 192.168.23.1: seq=13 time=8.056ms Reply from 192.168.23.1: seq=14 time=1.002ms Reply from 192.168.23.1: seq=15 time=1.002ms Reply from 192.168.23.1: seq=16 time=1.093ms Reply from 192.168.23.1: seq=17 time=1.050ms Reply from 192.168.23.1: seq=18 time=1.972ms Reply from 192.168.23.1: seq=19 time=0.946ms Reply from 192.168.23.1: seq=20 time=0.916ms Reply from 192.168.23.1: seq=21 time=1.059ms Reply from 192.168.23.1: seq=22 time=0.997ms Reply from 192.168.23.1: seq=23 time=1.087ms Reply from 192.168.23.1: seq=24 time=0.937ms Reply from 192.168.23.1: seq=25 time=0.973ms Reply from 192.168.23.1: seq=26 time=0.916ms Reply from 192.168.23.1: seq=27 time=0.954ms Reply from 192.168.23.1: seq=28 time=1.122ms Reply from 192.168.23.1: seq=29 time=0.993ms Reply from 192.168.23.1: seq=30 time=0.974ms Reply from 192.168.23.1: seq=31 time=1.022ms Reply from 192.168.23.1: seq=32 time=0.971ms Reply from 192.168.23.1: seq=33 time=1.024ms Reply from 192.168.23.1: seq=34 time=0.912ms Reply from 192.168.23.1: seq=35 time=0.965ms Reply from 192.168.23.1: seq=36 time=1.090ms Reply from 192.168.23.1: seq=37 time=1.240ms Reply from 192.168.23.1: seq=38 time=0.957ms Reply from 192.168.23.1: seq=39 time=1.083ms Reply from 192.168.23.1: seq=40 time=0.944ms Reply from 192.168.23.1: seq=41 time=0.971ms Reply from 192.168.23.1: seq=42 time=1.880ms Reply from 192.168.23.1: seq=43 time=1.020ms Reply from 192.168.23.1: seq=44 time=1.073ms Reply from 192.168.23.1: seq=45 time=0.969ms Reply from 192.168.23.1: seq=46 time=1.091ms Reply from 192.168.23.1: seq=47 time=4.338ms Reply from 192.168.23.1: seq=48 time=1.029ms Reply from 192.168.23.1: seq=49 time=1.070ms Reply from 192.168.23.1: seq=50 time=0.992ms Reply from 192.168.23.1: seq=51 time=1.107ms Reply from 192.168.23.1: seq=52 time=1.043ms Reply from 192.168.23.1: seq=53 time=1.140ms Reply from 192.168.23.1: seq=54 time=1.045ms Reply from 192.168.23.1: seq=55 time=1.039ms Reply from 192.168.23.1: seq=56 time=0.972ms Reply from 192.168.23.1: seq=57 time=1.034ms Reply from 192.168.23.1: seq=58 time=1.005ms Reply from 192.168.23.1: seq=59 time=13.924ms Reply from 192.168.23.1: seq=60 time=1.904ms Reply from 192.168.23.1: seq=61 time=0.911ms Reply from 192.168.23.1: seq=62 time=0.807ms Reply from 192.168.23.1: seq=63 time=1.078ms Reply from 192.168.23.1: seq=64 time=1.008ms Reply from 192.168.23.1: seq=65 time=1.031ms Reply from 192.168.23.1: seq=66 time=1.154ms Reply from 192.168.23.1: seq=67 time=1.020ms Reply from 192.168.23.1: seq=68 time=0.970ms Reply from 192.168.23.1: seq=69 time=6.911ms Reply from 192.168.23.1: seq=70 time=0.966ms Reply from 192.168.23.1: seq=71 time=0.960ms Reply from 192.168.23.1: seq=72 time=0.947ms Reply from 192.168.23.1: seq=73 time=0.971ms Reply from 192.168.23.1: seq=74 time=1.006ms Reply from 192.168.23.1: seq=75 time=1.062ms Reply from 192.168.23.1: seq=76 time=1.950ms Reply from 192.168.23.1: seq=77 time=1.159ms Reply from 192.168.23.1: seq=78 time=0.942ms Reply from 192.168.23.1: seq=79 time=0.979ms Reply from 192.168.23.1: seq=80 time=1.024ms Reply from 192.168.23.1: seq=81 time=1.100ms Reply from 192.168.23.1: seq=82 time=1.002ms Reply from 192.168.23.1: seq=83 time=0.964ms Reply from 192.168.23.1: seq=84 time=0.959ms Reply from 192.168.23.1: seq=85 time=0.941ms Reply from 192.168.23.1: seq=86 time=3.217ms Reply from 192.168.23.1: seq=87 time=1.004ms Reply from 192.168.23.1: seq=88 time=1.031ms Reply from 192.168.23.1: seq=89 time=0.965ms Reply from 192.168.23.1: seq=90 time=0.890ms Reply from 192.168.23.1: seq=91 time=1.139ms Reply from 192.168.23.1: seq=92 time=1.142ms Reply from 192.168.23.1: seq=93 time=8.522ms Reply from 192.168.23.1: seq=94 time=1.317ms Reply from 192.168.23.1: seq=95 time=0.954ms Reply from 192.168.23.1: seq=96 time=0.993ms Reply from 192.168.23.1: seq=97 time=1.010ms Reply from 192.168.23.1: seq=98 time=1.005ms Reply from 192.168.23.1: seq=99 time=1.014ms Reply from 192.168.23.1: seq=100 time=0.981ms Reply from 192.168.23.1: seq=101 time=1.304ms Reply from 192.168.23.1: seq=102 time=0.923ms Reply from 192.168.23.1: seq=103 time=2.283ms Reply from 192.168.23.1: seq=104 time=1.065ms --- Ping statistics --- 105 packets transmitted, 105 received, 0.0% packet loss round-trip min/avg/max/stddev = 0.807/1.469/13.924/1.763 ms # 테스트 2 : 노트북 ->유선->공유기#2(192.168.23.1)->유선->공유기#1(192.168.68.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.68.1 Pinging 192.168.68.1 with 32 bytes of data: Reply from 192.168.68.1: seq=0 time=1.486ms Reply from 192.168.68.1: seq=1 time=2.114ms Reply from 192.168.68.1: seq=2 time=1.337ms Reply from 192.168.68.1: seq=3 time=1.376ms Reply from 192.168.68.1: seq=4 time=1.338ms Reply from 192.168.68.1: seq=5 time=1.470ms Reply from 192.168.68.1: seq=6 time=1.492ms Reply from 192.168.68.1: seq=7 time=1.558ms Reply from 192.168.68.1: seq=8 time=5.329ms Reply from 192.168.68.1: seq=9 time=1.796ms Reply from 192.168.68.1: seq=10 time=1.431ms Reply from 192.168.68.1: seq=11 time=1.303ms Reply from 192.168.68.1: seq=12 time=1.347ms Reply from 192.168.68.1: seq=13 time=4.527ms Reply from 192.168.68.1: seq=14 time=1.243ms Reply from 192.168.68.1: seq=15 time=1.457ms Reply from 192.168.68.1: seq=16 time=1.162ms Reply from 192.168.68.1: seq=17 time=1.440ms Reply from 192.168.68.1: seq=18 time=9.523ms Reply from 192.168.68.1: seq=19 time=1.321ms Reply from 192.168.68.1: seq=20 time=1.229ms Reply from 192.168.68.1: seq=21 time=1.292ms Reply from 192.168.68.1: seq=22 time=1.398ms Reply from 192.168.68.1: seq=23 time=1.239ms Reply from 192.168.68.1: seq=24 time=1.214ms Reply from 192.168.68.1: seq=25 time=5.787ms Reply from 192.168.68.1: seq=26 time=1.301ms Reply from 192.168.68.1: seq=27 time=5.400ms Reply from 192.168.68.1: seq=28 time=2.135ms Reply from 192.168.68.1: seq=29 time=1.203ms Reply from 192.168.68.1: seq=30 time=1.376ms Reply from 192.168.68.1: seq=31 time=1.224ms Reply from 192.168.68.1: seq=32 time=1.766ms Reply from 192.168.68.1: seq=33 time=1.623ms Reply from 192.168.68.1: seq=34 time=1.525ms Reply from 192.168.68.1: seq=35 time=1.261ms Reply from 192.168.68.1: seq=36 time=1.351ms Reply from 192.168.68.1: seq=37 time=1.152ms Reply from 192.168.68.1: seq=38 time=1.892ms Reply from 192.168.68.1: seq=39 time=1.303ms Reply from 192.168.68.1: seq=40 time=1.351ms Reply from 192.168.68.1: seq=41 time=1.439ms Reply from 192.168.68.1: seq=42 time=1.352ms Reply from 192.168.68.1: seq=43 time=1.368ms Reply from 192.168.68.1: seq=44 time=1.391ms Reply from 192.168.68.1: seq=45 time=1.272ms Reply from 192.168.68.1: seq=46 time=1.327ms Reply from 192.168.68.1: seq=47 time=4.642ms Reply from 192.168.68.1: seq=48 time=1.321ms Reply from 192.168.68.1: seq=49 time=1.421ms Reply from 192.168.68.1: seq=50 time=1.328ms Reply from 192.168.68.1: seq=51 time=1.183ms Reply from 192.168.68.1: seq=52 time=1.578ms Reply from 192.168.68.1: seq=53 time=1.339ms Reply from 192.168.68.1: seq=54 time=1.356ms Reply from 192.168.68.1: seq=55 time=1.231ms Reply from 192.168.68.1: seq=56 time=1.391ms Reply from 192.168.68.1: seq=57 time=1.389ms Reply from 192.168.68.1: seq=58 time=1.248ms Reply from 192.168.68.1: seq=59 time=1.406ms Reply from 192.168.68.1: seq=60 time=1.411ms Reply from 192.168.68.1: seq=61 time=1.197ms Reply from 192.168.68.1: seq=62 time=1.227ms Reply from 192.168.68.1: seq=63 time=1.251ms Reply from 192.168.68.1: seq=64 time=1.308ms Reply from 192.168.68.1: seq=65 time=1.314ms Reply from 192.168.68.1: seq=66 time=1.304ms Reply from 192.168.68.1: seq=67 time=1.893ms Reply from 192.168.68.1: seq=68 time=1.217ms Reply from 192.168.68.1: seq=69 time=2.179ms Reply from 192.168.68.1: seq=70 time=1.365ms Reply from 192.168.68.1: seq=71 time=1.297ms Reply from 192.168.68.1: seq=72 time=1.542ms Reply from 192.168.68.1: seq=73 time=1.230ms Reply from 192.168.68.1: seq=74 time=1.349ms Reply from 192.168.68.1: seq=75 time=1.235ms Reply from 192.168.68.1: seq=76 time=1.584ms Reply from 192.168.68.1: seq=77 time=1.527ms Reply from 192.168.68.1: seq=78 time=1.346ms Reply from 192.168.68.1: seq=79 time=1.317ms Reply from 192.168.68.1: seq=80 time=1.237ms Reply from 192.168.68.1: seq=81 time=11.835ms Reply from 192.168.68.1: seq=82 time=1.465ms Reply from 192.168.68.1: seq=83 time=1.471ms Reply from 192.168.68.1: seq=84 time=1.420ms Reply from 192.168.68.1: seq=85 time=1.413ms Reply from 192.168.68.1: seq=86 time=17.853ms Reply from 192.168.68.1: seq=87 time=1.372ms Reply from 192.168.68.1: seq=88 time=1.318ms Reply from 192.168.68.1: seq=89 time=1.292ms Reply from 192.168.68.1: seq=90 time=1.305ms Reply from 192.168.68.1: seq=91 time=1.414ms Reply from 192.168.68.1: seq=92 time=1.292ms Reply from 192.168.68.1: seq=93 time=1.293ms Reply from 192.168.68.1: seq=94 time=1.368ms Reply from 192.168.68.1: seq=95 time=1.199ms Reply from 192.168.68.1: seq=96 time=1.261ms Reply from 192.168.68.1: seq=97 time=1.307ms Reply from 192.168.68.1: seq=98 time=2.218ms Reply from 192.168.68.1: seq=99 time=1.360ms Reply from 192.168.68.1: seq=100 time=1.277ms --- Ping statistics --- 101 packets transmitted, 101 received, 0.0% packet loss round-trip min/avg/max/stddev = 1.152/1.932/17.853/2.219 ms # 테스트 3 : 노트북 ->유선->공유기#1(192.168.68.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.68.1 Pinging 192.168.68.1 with 32 bytes of data: Reply from 192.168.68.1: seq=0 time=1.055ms Reply from 192.168.68.1: seq=1 time=1.056ms Reply from 192.168.68.1: seq=2 time=1.008ms Reply from 192.168.68.1: seq=3 time=1.065ms Reply from 192.168.68.1: seq=4 time=1.099ms Reply from 192.168.68.1: seq=5 time=1.016ms Reply from 192.168.68.1: seq=6 time=1.028ms Reply from 192.168.68.1: seq=7 time=1.110ms Reply from 192.168.68.1: seq=8 time=1.002ms Reply from 192.168.68.1: seq=9 time=1.009ms Reply from 192.168.68.1: seq=10 time=1.023ms Reply from 192.168.68.1: seq=11 time=1.106ms Reply from 192.168.68.1: seq=12 time=0.999ms Reply from 192.168.68.1: seq=13 time=1.083ms Reply from 192.168.68.1: seq=14 time=1.121ms Reply from 192.168.68.1: seq=15 time=0.988ms Reply from 192.168.68.1: seq=16 time=1.112ms Reply from 192.168.68.1: seq=17 time=1.031ms Reply from 192.168.68.1: seq=18 time=0.987ms Reply from 192.168.68.1: seq=19 time=1.135ms Reply from 192.168.68.1: seq=20 time=1.048ms Reply from 192.168.68.1: seq=21 time=1.095ms Reply from 192.168.68.1: seq=22 time=1.725ms Reply from 192.168.68.1: seq=23 time=0.968ms Reply from 192.168.68.1: seq=24 time=0.957ms Reply from 192.168.68.1: seq=25 time=1.109ms Reply from 192.168.68.1: seq=26 time=1.052ms Reply from 192.168.68.1: seq=27 time=1.132ms Reply from 192.168.68.1: seq=28 time=1.453ms Reply from 192.168.68.1: seq=29 time=0.996ms Reply from 192.168.68.1: seq=30 time=0.954ms Reply from 192.168.68.1: seq=31 time=1.069ms Reply from 192.168.68.1: seq=32 time=0.952ms Reply from 192.168.68.1: seq=33 time=1.190ms Reply from 192.168.68.1: seq=34 time=1.168ms Reply from 192.168.68.1: seq=35 time=1.078ms Reply from 192.168.68.1: seq=36 time=1.019ms Reply from 192.168.68.1: seq=37 time=1.041ms Reply from 192.168.68.1: seq=38 time=1.011ms Reply from 192.168.68.1: seq=39 time=1.122ms Reply from 192.168.68.1: seq=40 time=1.015ms Reply from 192.168.68.1: seq=41 time=1.094ms Reply from 192.168.68.1: seq=42 time=1.649ms Reply from 192.168.68.1: seq=43 time=1.072ms Reply from 192.168.68.1: seq=44 time=1.072ms Reply from 192.168.68.1: seq=45 time=1.286ms Reply from 192.168.68.1: seq=46 time=0.969ms Reply from 192.168.68.1: seq=47 time=1.614ms Reply from 192.168.68.1: seq=48 time=1.160ms Reply from 192.168.68.1: seq=49 time=1.120ms Reply from 192.168.68.1: seq=50 time=1.241ms Reply from 192.168.68.1: seq=51 time=1.107ms Reply from 192.168.68.1: seq=52 time=1.004ms Reply from 192.168.68.1: seq=53 time=2.730ms Reply from 192.168.68.1: seq=54 time=1.173ms Reply from 192.168.68.1: seq=55 time=1.075ms Reply from 192.168.68.1: seq=56 time=1.038ms Reply from 192.168.68.1: seq=57 time=1.034ms Reply from 192.168.68.1: seq=58 time=1.036ms Reply from 192.168.68.1: seq=59 time=1.143ms Reply from 192.168.68.1: seq=60 time=1.084ms Reply from 192.168.68.1: seq=61 time=1.067ms Reply from 192.168.68.1: seq=62 time=1.024ms Reply from 192.168.68.1: seq=63 time=0.903ms Reply from 192.168.68.1: seq=64 time=1.062ms Reply from 192.168.68.1: seq=65 time=1.000ms Reply from 192.168.68.1: seq=66 time=1.151ms Reply from 192.168.68.1: seq=67 time=1.084ms Reply from 192.168.68.1: seq=68 time=1.041ms Reply from 192.168.68.1: seq=69 time=1.026ms Reply from 192.168.68.1: seq=70 time=1.125ms Reply from 192.168.68.1: seq=71 time=1.049ms Reply from 192.168.68.1: seq=72 time=1.067ms Reply from 192.168.68.1: seq=73 time=0.952ms Reply from 192.168.68.1: seq=74 time=1.057ms Reply from 192.168.68.1: seq=75 time=1.028ms Reply from 192.168.68.1: seq=76 time=1.108ms Reply from 192.168.68.1: seq=77 time=1.057ms Reply from 192.168.68.1: seq=78 time=0.992ms Reply from 192.168.68.1: seq=79 time=1.020ms Reply from 192.168.68.1: seq=80 time=1.021ms Reply from 192.168.68.1: seq=81 time=1.111ms Reply from 192.168.68.1: seq=82 time=1.088ms Reply from 192.168.68.1: seq=83 time=0.990ms Reply from 192.168.68.1: seq=84 time=1.154ms Reply from 192.168.68.1: seq=85 time=1.081ms Reply from 192.168.68.1: seq=86 time=1.012ms Reply from 192.168.68.1: seq=87 time=1.143ms Reply from 192.168.68.1: seq=88 time=1.094ms Reply from 192.168.68.1: seq=89 time=1.072ms Reply from 192.168.68.1: seq=90 time=1.060ms Reply from 192.168.68.1: seq=91 time=0.936ms Reply from 192.168.68.1: seq=92 time=1.047ms Reply from 192.168.68.1: seq=93 time=1.005ms Reply from 192.168.68.1: seq=94 time=1.072ms Reply from 192.168.68.1: seq=95 time=1.087ms Reply from 192.168.68.1: seq=96 time=0.951ms Reply from 192.168.68.1: seq=97 time=1.071ms Reply from 192.168.68.1: seq=98 time=1.031ms Reply from 192.168.68.1: seq=99 time=1.079ms Reply from 192.168.68.1: seq=100 time=1.041ms Reply from 192.168.68.1: seq=101 time=1.094ms Reply from 192.168.68.1: seq=102 time=1.022ms Reply from 192.168.68.1: seq=103 time=0.907ms --- Ping statistics --- 104 packets transmitted, 104 received, 0.0% packet loss round-trip min/avg/max/stddev = 0.903/1.095/2.730/0.205 ms C:\Users\creer>
댓글11
-
세상의모든계산기
유선) hrping 핑 테스트
hrping.exe 192.168.23.1 -n 1000
This is hrPING v5.07.1150 by cFos Software GmbH -- https://www.cfos.de
(중략)
Packets: sent=1000, rcvd=1000, error=0, lost=0 (0.0% loss) in 499.511856 sec
RTTs in ms: min/avg/max/dev: 0.618 / 1.679 / 20.264 / 2.347
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.120
- 노트북->유선->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 유선 -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.4 port 4985 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 188 MBytes 786 Mbits/sec
[ 4] 2.00-4.00 sec 191 MBytes 800 Mbits/sec
[ 4] 4.00-6.00 sec 184 MBytes 771 Mbits/sec
[ 4] 6.00-8.00 sec 184 MBytes 770 Mbits/sec
[ 4] 8.00-10.00 sec 191 MBytes 800 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 936 MBytes 785 Mbits/sec sender
[ 4] 0.00-10.00 sec 936 MBytes 785 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64> -
세상의모든계산기
무선 2.4G) hrping 핑 테스트
Packets: sent=1000, rcvd=999, error=0, lost=1 (0.1% loss) in 499.507024 sec
RTTs in ms: min/avg/max/dev: 1.103 / 10.756 / 1793.124 / 80.016
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.119
- 노트북->무선(2.4G)->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 무선 2.4G -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.2 port 5129 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 47.5 MBytes 199 Mbits/sec
[ 4] 2.00-4.00 sec 52.0 MBytes 218 Mbits/sec
[ 4] 4.00-6.00 sec 50.4 MBytes 211 Mbits/sec
[ 4] 6.00-8.00 sec 50.6 MBytes 212 Mbits/sec
[ 4] 8.00-10.00 sec 49.0 MBytes 206 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 250 MBytes 209 Mbits/sec sender
[ 4] 0.00-10.00 sec 249 MBytes 209 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64> -
세상의모든계산기
비교 : AC-68U
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 65.0 MBytes 54.5 Mbits/sec sender
[ 4] 0.00-10.01 sec 65.0 MBytes 54.5 Mbits/sec receiver
이상해서 다시 접속
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.68.36 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.68.36, port 5000
[ 4] local 192.168.68.217 port 12792 connected to 192.168.68.36 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 22.4 MBytes 93.7 Mbits/sec
[ 4] 2.00-4.00 sec 24.5 MBytes 103 Mbits/sec
[ 4] 4.00-6.00 sec 23.6 MBytes 98.9 Mbits/sec
[ 4] 6.00-8.01 sec 24.2 MBytes 101 Mbits/sec
[ 4] 8.01-10.00 sec 24.1 MBytes 102 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 119 MBytes 99.7 Mbits/sec sender
[ 4] 0.00-10.00 sec 119 MBytes 99.7 Mbits/sec receiver
* 공유기 2.4G 연결된 장치가 많아서 연결속도/다운속도가 떨어지는 것이 아닌가 합니다.
-
세상의모든계산기
무선 5G) hrping 핑 테스트
Packets: sent=1000, rcvd=999, error=0, lost=1 (0.1% loss) in 499.511706 sec
RTTs in ms: min/avg/max/dev: 1.509 / 13.751 / 507.855 / 24.991
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.119
- 노트북->무선(5G)->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 무선 5G -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.2 port 5063 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 68.2 MBytes 286 Mbits/sec
[ 4] 2.00-4.00 sec 65.6 MBytes 276 Mbits/sec
[ 4] 4.00-6.00 sec 73.6 MBytes 309 Mbits/sec
[ 4] 6.00-8.00 sec 67.9 MBytes 285 Mbits/sec
[ 4] 8.00-10.00 sec 70.2 MBytes 294 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 346 MBytes 290 Mbits/sec sender
[ 4] 0.00-10.00 sec 346 MBytes 290 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64>
세상의모든계산기 님의 최근 댓글
수치해석 방법 method 를 강제로 선택할 수 있으면 좋을텐데... 위의 스샷을 보면 되는 듯 하면서도 아래 스샷을 보면 안되는 것 같기도 합니다. solve(Expr,[Var]) csolve(LstEq,LstVar) nSolve(Expr,Var,[Guess or Interval],[Method]) deSolve(Eq,[TimeVar],FncVar) linsolve(LstLinEq,LstVar) fsolve(Expr,Var,[Guess or Interval],[Method]) 2025 10.17 종합해서 답변을 드리면 HP Prime 에 solve 에서 변수명에 구간을 입력하면 수치해석 방식으로 bisection 을 사용함. 이 bisection 방식은 해의 좌-우 부호가 서로 바뀌어야만 해를 인식하고 해의 좌-우 부호가 같으면 해를 인식하지 못합니다. 이 때문에 본문 sin 의 예나 아래 사진의 예에서는 해를 인식하지 못하는 것으로 보입니다. 2025 10.17 Gemini-2.5-pro 답변 ✦ 현대 컴퓨터 대수 시스템(CAS) 계산기에 탑재된 solve 기능의 일반적인 내부 동작 원리에 대해 설명해 드리겠습니다. 현대 CAS의 solve 기능은 단순히 하나의 알고리즘으로 작동하는 것이 아니라, 마치 '순수 수학자'와 '문제 해결 공학자'가 협력하는 것처럼, 여러 단계에 걸친 정교한 '하이브리드(Hybrid)' 방식으로 동작합니다. solve 함수의 작동 과정 1단계: 기호적 해법 (Symbolic Solver) - '순수 수학자'의 접근 계산기는 가장 먼저 방정식을 대수적으로, 즉 정확한 수학적 해를 찾으려고 시도합니다. 이 단계는 마치 사람이 공식을 이용해 문제를 푸는 과정과 같습니다. 1. 방정식 분석: solve 명령을 받으면, 시스템은 먼저 입력된 방정식의 구조를 분석합니다. (예: 이것이 다항식인가? 삼각방정식인가? 로그방정식인가?) 2. 규칙 기반 풀이: 분석된 구조에 따라, 시스템은 내장된 방대한 수학 규칙 라이브러리를 적용합니다. * 선형/이차 방정식: ax+b=c 나 ax²+bx+c=0 같은 형태는 이항, 인수분해, 근의 공식 등을 이용해 즉시 풉니다. * 고차 다항식: 인수분해, 조립제법 등의 규칙을 적용하여 유리수 해를 찾습니다. * 삼각방정식: sin(x) = 0.5 와 같은 경우, x = nπ + (-1)ⁿ * (π/6) 와 같이 주기성을 고려한 일반해 공식을 적용합니다. * 기타: 로그, 지수 법칙 등 해당 방정식에 맞는 대수적 풀이법을 총동원합니다. 3. 결과: 이 단계에서 해를 찾으면, 1.414... 와 같은 근사값이 아닌 √2 나 π/3 와 같은 정확한 기호 형태의 해를 반환합니다. > 강점: 수학적으로 완벽하고 정확한 해를 제공합니다. > 한계: 대수적인 풀이법이 알려져 있지 않은 방정식(예: cos(x) = x 또는 eˣ = x+2)은 풀 수 없습니다. --- 2단계: 수치적 해법 (Numerical Solver) - '문제 해결 공학자'의 접근 만약 1단계의 '순수 수학자'가 "이건 공식으로 풀 수 없어"라고 결론 내리면, solve 기능은 포기하지 않고 2단계인 '문제 해결 공학자'에게 문제를 넘깁니다. 이 단계의 목표는 정확한 해는 아니더라도, 매우 정밀한 근사해를 찾는 것입니다. 1. 반복적 탐색: 수치적 해법은 방정식을 직접 푸는 것이 아니라, 해가 있을 만한 지점에서부터 시작하여 반복적인 계산을 통해 해에 점점 더 가까워지는 방식을 사용합니다. * 적당한 값을 추측해서 대입해 봅니다. * 결과가 0보다 큰지 작은지에 따라, 다음 추측값을 어느 방향으로 수정할지 결정합니다. * 이 과정을 수없이 반복하여 오차가 거의 0에 가까워질 때까지 해를 좁혀나갑니다. 2. 핵심 알고리즘: 이때 사용되는 대표적인 알고리즘은 다음과 같습니다. * 뉴턴-랩슨법 (Newton-Raphson Method): 미분(접선)을 이용하여 매우 빠른 속도로 해에 수렴하는 강력한 방법입니다. * 이분법 (Bisection Method): 해가 존재하는 특정 구간을 계속 절반으로 나누어 범위를 좁혀나가는 방식으로, 속도는 느리지만 안정적으로 해를 찾을 수 있습니다. 3. 결과: 이 단계가 성공하면, 시스템은 0.739085133215 와 같이 소수점 아래 여러 자리까지 표현되는 매우 정밀한 부동소수점 형태의 근사해를 반환합니다. > 강점: 대수적으로 풀 수 없는 복잡한 방정식의 해도 근사적으로 찾아낼 수 있습니다. > 한계: 근사해이며, 알고리즘의 특성상 특정 조건(예: 해가 중근을 갖는 경우)에서는 해를 찾지 못하고 실패할 수도 있습니다. 결론: 왜 하이브리드 방식인가? 분석 → 기호적 풀이 시도 → (실패 또는 불가능 시) → 수치적 풀이로 전환 이처럼 현대 CAS의 solve 기능은 정확성(기호적 해법)과 범용성(수치적 해법)이라는 두 마리 토끼를 모두 잡기 위해 설계된 정교한 협력 시스템입니다. 먼저 가장 이상적인 '정확한 해'를 추구하되, 그것이 불가능할 경우 차선책으로 '정밀한 근사해'라도 찾아내어 사용자에게 최대한의 결과를 제공하는 것입니다. 2025 10.17 hp prime 이 solve 함수에서 해를 찾는데 어떤 방법(method)을 사용하는지 공식적인 무서로 정확하게 파악되진 않습니다. 2025 10.17 참고 x=guess 는 iterative 방식(일반적으로는 newton's method를 의미함)을 x=xmin .. xmax 는 bisection 방식을 사용하는 듯 합니다. // 구간지정 개념과는 차이가 있는 듯? 2025 10.17