From 94fc4a7116d694b05a17f8d1565144ceb8dd1ff6 Mon Sep 17 00:00:00 2001 From: Vladimir Dubrovin <3proxy@3proxy.ru> Date: Mon, 12 Oct 2026 13:59:20 +0300 Subject: [PATCH] highload.html: benchmark figures, linked on devel The benchmarks live on the devel branch only, so link to their results there; master has no bench/. Co-Authored-By: Claude Opus 5.5 --- doc/html/highload.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/html/highload.html b/doc/html/highload.html index aa182c3..63d9934 100644 --- a/doc/html/highload.html +++ b/doc/html/highload.html @@ -674,8 +674,8 @@ server sends to the client (downloads), -s2 what the client sends to the server only where it pays. -s0, the default, turns it off. In builds without it (CMake option 3PROXY_USE_SPLICE=OFF, or -DWITHSPLICE removed from the Makefile) -s is accepted and ignored.

splice() pays off when most of the traffic is large transfers: in the -benchmarks it moved -1.4 to 1.7 times more data than the read/write path at about half the CPU per gigabyte. +benchmarks it moved +1.3 to 2.1 times more data than the read/write path at 40-55% less CPU per gigabyte. It does not help small requests and short connections, which go slower with it, and every spliced direction needs a pipe (two file descriptors) and more kernel buffer memory. Data filters are not applied to spliced data.