From 3066c64058e03c9b9e03b0621f9b3a19c25eb1d0 Mon Sep 17 00:00:00 2001 From: DarkCat09 Date: Mon, 18 Nov 2024 23:17:35 +0400 Subject: [PATCH] docs: add "in a nutshell" section --- README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1820b6e..9a3370f 100644 --- a/README.md +++ b/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, 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