From d89134be33c924216248efeb83d700d71ec1cbfc Mon Sep 17 00:00:00 2001 From: z3APA3A <3APA3A@3proxy.ru> Date: Tue, 5 Mar 2019 15:02:04 +0300 Subject: [PATCH] minor doc update --- doc/html/highload.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/html/highload.html b/doc/html/highload.html index 229ef7b..70916c5 100644 --- a/doc/html/highload.html +++ b/doc/html/highload.html @@ -84,8 +84,9 @@ If 3proxy is used in VPS environment, there can be additional limitations. For example, kernel resources / system CPU usage can be limited in a different way, and this can become a bottleneck. Since 0.9 devel, 3proxy uses splice() by default on Linux, splice() prevents network traffic from being copied from kernel space to 3proxy process and generally increases throughput, epecially in the case of high volume traffic. But -since some work is moved to kernel, it requires up to 2 times more system resources in terms of CPU and memory. -Use -s0 option to disable splice() usage for given service, if system resources are additionally limited, e.g. +since some work is moved to kernel, it requires up to 2 times more kernel resources in terms of CPU and memory. +Use -s0 option to disable splice() usage for given service, if kernel resources are additionally limited and this +limitation is a bottleneck, e.g. 
 
 socks -s0