mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
Benchmarks: automatic splice, CONNECT, SOCKS and TCP relay results
RESULTS.md now leads with devel as of the automatic splice mode (lazy pipes kept per connection): the HTTP proxy, CONNECT tunnels (against squid and tinyproxy), SOCKSv5 tunnels (against dante) and TCP relays (tcppm against nginx stream and haproxy mode tcp), each a copying and a splice table, on the M4 and Skylake hosts; 16 KB buffers against 64 KB. The earlier sessions follow. data/: *-auto-http.csv (HTTP proxy) and *-tunnels.csv (CONNECT, SOCKS, relay) for both machines. README.md: which proxies take part in which scenarios, reworded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a146570533
commit
eb11c617b7
6 files changed
+1452
-72
No files matched your search
+3
-3
@@ -79,9 +79,9 @@ host) falls on all of them alike; the summary gives medians.
|
||||
| `relay-*` | the same through a TCP relay to a fixed destination: 3proxy `tcppm`, nginx `stream`, haproxy `mode tcp` |
|
||||
|
||||
nginx is not a forward proxy: it answers absolute URIs by passing them to its
|
||||
upstream, which is the origin here, and it has no CONNECT or SOCKS, so only
|
||||
these scenarios compare like with like. Neither nginx nor haproxy has CONNECT or SOCKS, so they take part in the
|
||||
`relay-*` scenarios but not in the `connect-*` and `socks-*` ones. tinyproxy
|
||||
upstream, which is the origin here. Neither nginx nor haproxy has CONNECT or
|
||||
SOCKS, so they take part in the HTTP and `relay-*` scenarios but not in the
|
||||
`connect-*` and `socks-*` ones. tinyproxy
|
||||
and squid are HTTP proxies, measured in the HTTP and `connect-*` scenarios;
|
||||
dante is a SOCKS server, measured in the `socks-*` ones.
|
||||
|
||||
|
||||
Reference in new issue
Block a user