Ardupilot Rpanion 4GLTE 网络性能测试 - 国内中转

2024-05-14 23:44
文章标签 性能 网络 测试 国内 ardupilot 中转 4glte rpanion

本文主要是介绍Ardupilot Rpanion 4GLTE 网络性能测试 - 国内中转，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

Ardupilot Rpanion 4GLTE 网络性能测试 - 国内中转

  • 1. 源由
  • 2. 视频效果
    • 2.1 整体刷新率不高
    • 2.2 网络延迟可接受
    • 2.3 带宽增加丢包明显
    • 2.4 实测效果流畅
  • 3. 总结

1. 源由

上一次，由于ZeroTier使用了国外服务器，延迟~ 569 ms，花屏、卡顿。

本着不折腾到底，誓不罢休的精神，本次我们将ZeroTier切换到了国内中转服务器。

在这里插入图片描述

2. 视频效果

最终视频效果是王道！来我们看下效果。

Ardupilot Rpanion 4GLTE-4GLTE Domestic Routing Copter

2.1 整体刷新率不高

一般都能到59FPS，但是显示器今天不知道怎么只有30FPS，有的时候都不到。
刷新率越差，误差就越大。

2.2 网络延迟可接受

ping延迟不高，大约在[64ms, 306ms]，平均117ms。

ping -t 192.168.235.73Pinging 192.168.235.73 with 32 bytes of data:
Reply from 192.168.235.73: bytes=32 time=103ms TTL=64
Reply from 192.168.235.73: bytes=32 time=102ms TTL=64
Reply from 192.168.235.73: bytes=32 time=109ms TTL=64
Reply from 192.168.235.73: bytes=32 time=128ms TTL=64
Reply from 192.168.235.73: bytes=32 time=127ms TTL=64
Reply from 192.168.235.73: bytes=32 time=154ms TTL=64
Reply from 192.168.235.73: bytes=32 time=113ms TTL=64
Reply from 192.168.235.73: bytes=32 time=94ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=131ms TTL=64
Reply from 192.168.235.73: bytes=32 time=120ms TTL=64
Reply from 192.168.235.73: bytes=32 time=121ms TTL=64
Reply from 192.168.235.73: bytes=32 time=101ms TTL=64
Reply from 192.168.235.73: bytes=32 time=115ms TTL=64
Reply from 192.168.235.73: bytes=32 time=129ms TTL=64
Reply from 192.168.235.73: bytes=32 time=112ms TTL=64
Reply from 192.168.235.73: bytes=32 time=192ms TTL=64
Reply from 192.168.235.73: bytes=32 time=101ms TTL=64
Reply from 192.168.235.73: bytes=32 time=105ms TTL=64
Reply from 192.168.235.73: bytes=32 time=99ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=97ms TTL=64
Reply from 192.168.235.73: bytes=32 time=91ms TTL=64
Reply from 192.168.235.73: bytes=32 time=115ms TTL=64
Reply from 192.168.235.73: bytes=32 time=102ms TTL=64
Reply from 192.168.235.73: bytes=32 time=169ms TTL=64
Reply from 192.168.235.73: bytes=32 time=113ms TTL=64
Reply from 192.168.235.73: bytes=32 time=119ms TTL=64
Reply from 192.168.235.73: bytes=32 time=83ms TTL=64
Reply from 192.168.235.73: bytes=32 time=108ms TTL=64
Reply from 192.168.235.73: bytes=32 time=147ms TTL=64
Reply from 192.168.235.73: bytes=32 time=132ms TTL=64
Reply from 192.168.235.73: bytes=32 time=111ms TTL=64
Reply from 192.168.235.73: bytes=32 time=156ms TTL=64
Reply from 192.168.235.73: bytes=32 time=113ms TTL=64
Reply from 192.168.235.73: bytes=32 time=100ms TTL=64
Reply from 192.168.235.73: bytes=32 time=114ms TTL=64
Reply from 192.168.235.73: bytes=32 time=127ms TTL=64
Reply from 192.168.235.73: bytes=32 time=99ms TTL=64
Reply from 192.168.235.73: bytes=32 time=85ms TTL=64
Reply from 192.168.235.73: bytes=32 time=88ms TTL=64
Reply from 192.168.235.73: bytes=32 time=113ms TTL=64
Reply from 192.168.235.73: bytes=32 time=111ms TTL=64
Reply from 192.168.235.73: bytes=32 time=106ms TTL=64
Reply from 192.168.235.73: bytes=32 time=116ms TTL=64
Reply from 192.168.235.73: bytes=32 time=117ms TTL=64
Reply from 192.168.235.73: bytes=32 time=104ms TTL=64
Reply from 192.168.235.73: bytes=32 time=105ms TTL=64
Reply from 192.168.235.73: bytes=32 time=99ms TTL=64
Reply from 192.168.235.73: bytes=32 time=101ms TTL=64
Reply from 192.168.235.73: bytes=32 time=111ms TTL=64
Reply from 192.168.235.73: bytes=32 time=86ms TTL=64
Reply from 192.168.235.73: bytes=32 time=144ms TTL=64
Reply from 192.168.235.73: bytes=32 time=81ms TTL=64
Reply from 192.168.235.73: bytes=32 time=79ms TTL=64
Reply from 192.168.235.73: bytes=32 time=94ms TTL=64
Reply from 192.168.235.73: bytes=32 time=132ms TTL=64
Reply from 192.168.235.73: bytes=32 time=92ms TTL=64
Reply from 192.168.235.73: bytes=32 time=96ms TTL=64
Reply from 192.168.235.73: bytes=32 time=121ms TTL=64
Reply from 192.168.235.73: bytes=32 time=133ms TTL=64
Reply from 192.168.235.73: bytes=32 time=127ms TTL=64
Reply from 192.168.235.73: bytes=32 time=97ms TTL=64
Reply from 192.168.235.73: bytes=32 time=127ms TTL=64
Reply from 192.168.235.73: bytes=32 time=135ms TTL=64
Reply from 192.168.235.73: bytes=32 time=96ms TTL=64
Reply from 192.168.235.73: bytes=32 time=120ms TTL=64
Reply from 192.168.235.73: bytes=32 time=101ms TTL=64
Reply from 192.168.235.73: bytes=32 time=135ms TTL=64
Reply from 192.168.235.73: bytes=32 time=144ms TTL=64
Reply from 192.168.235.73: bytes=32 time=107ms TTL=64
Reply from 192.168.235.73: bytes=32 time=112ms TTL=64
Reply from 192.168.235.73: bytes=32 time=139ms TTL=64
Reply from 192.168.235.73: bytes=32 time=81ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=116ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=162ms TTL=64
Reply from 192.168.235.73: bytes=32 time=119ms TTL=64
Reply from 192.168.235.73: bytes=32 time=120ms TTL=64
Reply from 192.168.235.73: bytes=32 time=306ms TTL=64
Reply from 192.168.235.73: bytes=32 time=143ms TTL=64
Reply from 192.168.235.73: bytes=32 time=80ms TTL=64
Reply from 192.168.235.73: bytes=32 time=94ms TTL=64
Reply from 192.168.235.73: bytes=32 time=91ms TTL=64
Reply from 192.168.235.73: bytes=32 time=156ms TTL=64
Reply from 192.168.235.73: bytes=32 time=114ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=129ms TTL=64
Reply from 192.168.235.73: bytes=32 time=184ms TTL=64
Reply from 192.168.235.73: bytes=32 time=110ms TTL=64
Reply from 192.168.235.73: bytes=32 time=135ms TTL=64
Reply from 192.168.235.73: bytes=32 time=144ms TTL=64
Reply from 192.168.235.73: bytes=32 time=141ms TTL=64
Reply from 192.168.235.73: bytes=32 time=79ms TTL=64
Reply from 192.168.235.73: bytes=32 time=78ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=128ms TTL=64
Reply from 192.168.235.73: bytes=32 time=206ms TTL=64
Reply from 192.168.235.73: bytes=32 time=129ms TTL=64
Reply from 192.168.235.73: bytes=32 time=126ms TTL=64
Reply from 192.168.235.73: bytes=32 time=154ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=94ms TTL=64
Reply from 192.168.235.73: bytes=32 time=125ms TTL=64
Reply from 192.168.235.73: bytes=32 time=90ms TTL=64
Reply from 192.168.235.73: bytes=32 time=129ms TTL=64
Reply from 192.168.235.73: bytes=32 time=111ms TTL=64
Reply from 192.168.235.73: bytes=32 time=113ms TTL=64
Reply from 192.168.235.73: bytes=32 time=106ms TTL=64
Reply from 192.168.235.73: bytes=32 time=94ms TTL=64
Reply from 192.168.235.73: bytes=32 time=92ms TTL=64
Reply from 192.168.235.73: bytes=32 time=96ms TTL=64
Reply from 192.168.235.73: bytes=32 time=114ms TTL=64
Reply from 192.168.235.73: bytes=32 time=122ms TTL=64
Reply from 192.168.235.73: bytes=32 time=93ms TTL=64
Reply from 192.168.235.73: bytes=32 time=165ms TTL=64
Reply from 192.168.235.73: bytes=32 time=135ms TTL=64
Reply from 192.168.235.73: bytes=32 time=185ms TTL=64
Reply from 192.168.235.73: bytes=32 time=124ms TTL=64
Reply from 192.168.235.73: bytes=32 time=64ms TTL=64
Reply from 192.168.235.73: bytes=32 time=89ms TTL=64
Reply from 192.168.235.73: bytes=32 time=84ms TTL=64
Reply from 192.168.235.73: bytes=32 time=90ms TTL=64
Reply from 192.168.235.73: bytes=32 time=112ms TTL=64
Reply from 192.168.235.73: bytes=32 time=92ms TTL=64
Reply from 192.168.235.73: bytes=32 time=90ms TTL=64
Reply from 192.168.235.73: bytes=32 time=78ms TTL=64
Reply from 192.168.235.73: bytes=32 time=129ms TTL=64Ping statistics for 192.168.235.73:Packets: Sent = 129, Received = 129, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:Minimum = 64ms, Maximum = 306ms, Average = 117ms
Control-C

2.3 带宽增加丢包明显

iperf情况很诡异：相较于《Ardupilot Rpanion iperf网络性能测试》情况更差，但是实际效果不错。

在这里插入图片描述

$ iperf -b 300pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2627 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 47594 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   410 KBytes  3.36 Mbits/sec  301/0      302 pps
[  3] 1.0000-2.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 2.0000-3.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 3.0000-4.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 4.0000-5.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 5.0000-6.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 6.0000-7.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 7.0000-8.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 8.0000-9.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 9.0000-10.0000 sec   410 KBytes  3.36 Mbits/sec  300/0      300 pps
[  3] 0.0000-10.0069 sec  4.01 MBytes  3.36 Mbits/sec  3005/0      300 pps
[  3] Sent 3005 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-10.0125 sec  4.01 MBytes  3.36 Mbits/sec   5.955 ms    0/ 3004 (0%)$ iperf -b 350pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2690 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 43876 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   479 KBytes  3.92 Mbits/sec  351/0      352 pps
[  3] 1.0000-2.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 2.0000-3.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 3.0000-4.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 4.0000-5.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 5.0000-6.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 6.0000-7.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 7.0000-8.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 8.0000-9.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 9.0000-10.0000 sec   479 KBytes  3.92 Mbits/sec  350/0      350 pps
[  3] 0.0000-10.0059 sec  4.68 MBytes  3.92 Mbits/sec  3505/0      350 pps
[  3] Sent 3505 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-10.0302 sec  4.68 MBytes  3.91 Mbits/sec   5.143 ms    0/ 3504 (0%)$ iperf -b 400pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2697 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 33690 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   547 KBytes  4.48 Mbits/sec  401/0      402 pps
[  3] 1.0000-2.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 2.0000-3.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 3.0000-4.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 4.0000-5.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 5.0000-6.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 6.0000-7.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 7.0000-8.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 8.0000-9.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 9.0000-10.0000 sec   547 KBytes  4.48 Mbits/sec  400/0      400 pps
[  3] 0.0000-10.0028 sec  5.34 MBytes  4.48 Mbits/sec  4004/0      400 pps
[  3] Sent 4004 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-10.0392 sec  5.34 MBytes  4.46 Mbits/sec   4.412 ms    0/ 4003 (0%)$ iperf -b 500pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2709 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 44078 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   684 KBytes  5.60 Mbits/sec  501/0      502 pps
[  3] 1.0000-2.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 2.0000-3.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 3.0000-4.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 4.0000-5.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 5.0000-6.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 6.0000-7.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 7.0000-8.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 8.0000-9.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 9.0000-10.0000 sec   684 KBytes  5.60 Mbits/sec  500/0      500 pps
[  3] 0.0000-10.0042 sec  6.68 MBytes  5.60 Mbits/sec  5005/0      500 pps
[  3] Sent 5005 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-10.1477 sec  5.67 MBytes  4.69 Mbits/sec  11.400 ms  756/ 5005 (15%)$ iperf -b 550pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2716 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 49192 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   752 KBytes  6.16 Mbits/sec  551/0      552 pps
[  3] 1.0000-2.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 2.0000-3.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 3.0000-4.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 4.0000-5.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 5.0000-6.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 6.0000-7.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 7.0000-8.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 8.0000-9.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 9.0000-10.0000 sec   752 KBytes  6.16 Mbits/sec  550/0      550 pps
[  3] 0.0000-10.0040 sec  7.35 MBytes  6.16 Mbits/sec  5505/0      550 pps
[  3] Sent 5505 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-9.9913 sec  5.62 MBytes  4.72 Mbits/sec   3.449 ms 1293/ 5504 (23%)$ iperf -b 600pps -u -e -i 1 -l 1400  -c 192.168.235.63
------------------------------------------------------------
Client connecting to 192.168.235.63, UDP port 5001 with pid 2724 (1 flows)
Write buffer size: 1.37 KByte
UDP buffer size:  208 KByte (default)
------------------------------------------------------------
[  3] local 192.168.235.73%ztjjfduqpe port 49983 connected with 192.168.235.63 port 5001
[ ID] Interval            Transfer     Bandwidth      Write/Err  PPS
[  3] 0.0000-1.0000 sec   820 KBytes  6.72 Mbits/sec  601/0      602 pps
[  3] 1.0000-2.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 2.0000-3.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 3.0000-4.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 4.0000-5.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 5.0000-6.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 6.0000-7.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 7.0000-8.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 8.0000-9.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 9.0000-10.0000 sec   820 KBytes  6.72 Mbits/sec  600/0      600 pps
[  3] 0.0000-10.0035 sec  8.01 MBytes  6.72 Mbits/sec  6005/0      600 pps
[  3] Sent 6005 datagrams
[  3] Server Report:
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3] 0.0000-9.9823 sec  5.55 MBytes  4.66 Mbits/sec   3.217 ms 1847/ 6004 (31%)

2.4 实测效果流畅

实测~ 251 ms 时延； 平均延时117/2 = 58.5 ms, 251 - 58.5 = 192.5 ms左右

在这里插入图片描述

3. 总结

综合上面的情况，整体分析：

  1. 上述网络配置情况，视频基本流畅，无雪花，卡顿，性能基本OK，可进行外场测试
  2. 计算机刷屏FPS未能稳定维持在59FPS，待查测试环境
  3. 部分截图发现，延迟甚至有1s之久，可能与刷屏或者最差网络环境有关
  4. 实测时需要关注不稳定的4GLTE网络，以及最差情况是否出现卡顿或者延迟问题

好了，小伙伴们，等我外场测试的好消息！ ：）

这篇关于Ardupilot Rpanion 4GLTE 网络性能测试 - 国内中转的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/990195。

相关文章

SpringBoot中整合RabbitMQ(测试+部署上线最新完整)的过程

SpringBoot中整合RabbitMQ(测试+部署上线最新完整)的过程

《SpringBoot中整合RabbitMQ(测试+部署上线最新完整)的过程》本文详细介绍了如何在虚拟机和宝塔面板中安装RabbitMQ,并使用Java代码实现消息的发送和接收,通过异步通讯,可以优化... 目录一、RabbitMQ安装二、启动RabbitMQ三、javascript编写Java代码1、引入
阅读更多...
Nginx设置连接超时并进行测试的方法步骤

Nginx设置连接超时并进行测试的方法步骤

《Nginx设置连接超时并进行测试的方法步骤》在高并发场景下,如果客户端与服务器的连接长时间未响应,会占用大量的系统资源,影响其他正常请求的处理效率,为了解决这个问题,可以通过设置Nginx的连接... 目录设置连接超时目的操作步骤测试连接超时测试方法：总结：设置连接超时目的设置客户端与服务器之间的连接
阅读更多...
Python使用国内镜像加速pip安装的方法讲解

Python使用国内镜像加速pip安装的方法讲解

《Python使用国内镜像加速pip安装的方法讲解》在Python开发中,pip是一个非常重要的工具,用于安装和管理Python的第三方库,然而,在国内使用pip安装依赖时,往往会因为网络问题而导致速... 目录一、pip 工具简介1. 什么是 pip？2. 什么是 -i 参数？二、国内镜像源的选择三、如何
阅读更多...
Springboot中分析SQL性能的两种方式详解

Springboot中分析SQL性能的两种方式详解

《Springboot中分析SQL性能的两种方式详解》文章介绍了SQL性能分析的两种方式：MyBatis-Plus性能分析插件和p6spy框架,MyBatis-Plus插件配置简单,适用于开发和测试环... 目录SQL性能分析的两种方式:功能介绍实现方式:实现步骤:SQL性能分析的两种方式:功能介绍记录
阅读更多...
如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别详解

如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别详解

《如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别详解》：本文主要介绍如何通过海康威视设备网络SDK进行Java二次开发摄像头车牌识别的相关资料,描述了如何使用海康威视设备网络SD... 目录前言开发流程问题和解决方案dll库加载不到的问题老旧版本sdk不兼容的问题关键实现流程总结前言作为
阅读更多...
Tomcat高效部署与性能优化方式

Tomcat高效部署与性能优化方式

《Tomcat高效部署与性能优化方式》本文介绍了如何高效部署Tomcat并进行性能优化,以确保Web应用的稳定运行和高效响应,高效部署包括环境准备、安装Tomcat、配置Tomcat、部署应用和启动T... 目录Tomcat高效部署与性能优化一、引言二、Tomcat高效部署三、Tomcat性能优化总结Tom
阅读更多...
C#使用yield关键字实现提升迭代性能与效率

C#使用yield关键字实现提升迭代性能与效率

《C#使用yield关键字实现提升迭代性能与效率》yield关键字在C#中简化了数据迭代的方式,实现了按需生成数据,自动维护迭代状态,本文主要来聊聊如何使用yield关键字实现提升迭代性能与效率,感兴... 目录前言传统迭代和yield迭代方式对比yield延迟加载按需获取数据yield break显式示迭
阅读更多...
SSID究竟是什么? WiFi网络名称及工作方式解析

SSID究竟是什么? WiFi网络名称及工作方式解析

《SSID究竟是什么?WiFi网络名称及工作方式解析》SID可以看作是无线网络的名称，类似于有线网络中的网络名称或者路由器的名称,在无线网络中，设备通过SSID来识别和连接到特定的无线网络... 当提到 Wi-Fi 网络时，就避不开「SSID」这个术语。简单来说，SSID 就是 Wi-Fi 网络的名称。比如
阅读更多...
Java实现任务管理器性能网络监控数据的方法详解

Java实现任务管理器性能网络监控数据的方法详解

《Java实现任务管理器性能网络监控数据的方法详解》在现代操作系统中,任务管理器是一个非常重要的工具,用于监控和管理计算机的运行状态,包括CPU使用率、内存占用等,对于开发者和系统管理员来说,了解这些... 目录引言一、背景知识二、准备工作1. Maven依赖2. Gradle依赖三、代码实现四、代码详解五
阅读更多...
如何测试计算机的内存是否存在问题? 判断电脑内存故障的多种方法

如何测试计算机的内存是否存在问题? 判断电脑内存故障的多种方法

《如何测试计算机的内存是否存在问题?判断电脑内存故障的多种方法》内存是电脑中非常重要的组件之一，如果内存出现故障，可能会导致电脑出现各种问题，如蓝屏、死机、程序崩溃等，如何判断内存是否出现故障呢？下... 如果你的电脑是崩溃、冻结还是不稳定，那么它的内存可能有问题。要进行检查，你可以使用Windows 11
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2