docs: add "in a nutshell" section
This commit is contained in:
parent
909d9d0a9c
commit
3066c64058
1 changed files with 12 additions and 1 deletions
13
README.md
13
README.md
|
@ -6,7 +6,18 @@ client commands are shown in `bench_*.txt` files.
|
||||||
All you need is iperf3 on client and server, hyperfine on client,
|
All you need is iperf3 on client and server, hyperfine on client,
|
||||||
xray and sing-box binaries (take from "Releases" or compile by yourself) placed on client and server.
|
xray and sing-box binaries (take from "Releases" or compile by yourself) placed on client and server.
|
||||||
|
|
||||||
Results in a nutshell: (TODO)
|
## In a nutshell
|
||||||
|
|
||||||
|
Results are inaccurate, they look like a statistical error, made by,
|
||||||
|
for example, different ISP's network load, that's why I said "an attempt on benchmarking".
|
||||||
|
|
||||||
|
Both proxies are almost the same speed. *Xray was sometimes a bit faster.*
|
||||||
|
But in iperf3 benchmark it often behaved weird: from 2nd packet speed was dropping to zero.
|
||||||
|
|
||||||
|
So, use what you want / to what you already get used / what works better in your case.
|
||||||
|
As for me, I found sing-box' JSON config more convenient than Xray's.
|
||||||
|
On the other hand, Xray provides more features to hide a proxy,
|
||||||
|
that is important, I guess (?), in China and Iran.
|
||||||
|
|
||||||
## hyperfine, curl, direct outbound
|
## hyperfine, curl, direct outbound
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue