ZT moved into the LINUX kernel, WIREGUARD can run up to 1000M on the A53 CPU
Using ZT can only run to 130M and use ZT version 1.64 to test,
Using the X86 32 core, the speed is less than 300M
Another fatal problem is jitter
The following is the result of my test in the local area network, extracting a period of unstable delay
64 bytes from 29.246.236.173: seq=661 ttl=64 time=2.218 ms
64 bytes from 29.246.236.173: seq=662 ttl=64 time=2.232 ms
64 bytes from 29.246.236.173: seq=663 ttl=64 time=2.276 ms
64 bytes from 29.246.236.173: seq=660 ttl=64 time=73.397 ms
64 bytes from 29.246.236.173: seq=20 ttl=64 time=2.250 ms
64 bytes from 29.246.236.173: seq=21 ttl=64 time=4384.932 ms
64 bytes from 29.246.236.173: seq=22 ttl=64 time=3385.697 ms
64 bytes from 29.246.236.173: seq=23 ttl=64 time=2385.454 ms
64 bytes from 29.246.236.173: seq=24 ttl=64 time=1385.250 ms
64 bytes from 29.246.236.173: seq=25 ttl=64 time=385.068 ms
64 bytes from 29.246.236.173: seq=26 ttl=64 time=2.231 ms
64 bytes from 29.246.236.173: seq=27 ttl=64 time=2.276 ms
— 29.246.236.173 ping statistics —
718 packets transmitted, 718 packets received, 0% packet loss
round-trip min/avg/max = 1.625/19.995/4384.932 ms
Maximum delay 4384ms
Similar to video conferencing, VOIP, online games, applications that are sensitive to delay and jitter, I now use WIREGUARD, hoping to move into the kernel as soon as possible to solve the jitter problem
The jitter problem has existed since I started using version 1.2.4, and I hope I can focus on it.