bughz/3proxy
1
0
Fork 0
mirror of https://github.com/3proxy/3proxy.git synced 2025-02-23 10:35:40 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

update for highload documentation

Browse Source
This commit is contained in:
z3APA3A 2017-10-06 21:17:15 +03:00
parent e588dce959
commit 29b834cf56
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/html/highload.html
View File

@ -189,8 +189,8 @@ you can eliminate Nagle's algorithm delay with TCP_NODELAY flag. Usage example:
proxy -osTCP_NODELAY -ocTCP_NODELAY proxy -osTCP_NODELAY -ocTCP_NODELAY
</pre> </pre>
sets TCP_NODELAY for client (oc) and server (os) connections. sets TCP_NODELAY for client (oc) and server (os) connections.
<pre> <p>Do not use TCP_NODELAY on slow connections, if connection bandwidth is
</pre> bottleneck, or because it may be more bandwidth-consuming.
<h4>Use slice to speedup large data amount transfers</h4> <h4>Use slice to speedup large data amount transfers</h4>
slice() allows to copy data between connections without copying to process slice() allows to copy data between connections without copying to process
addres space. It can speedup proxy on high bandwidth connections, if most addres space. It can speedup proxy on high bandwidth connections, if most
@ -203,3 +203,7 @@ devel version. Do not use it in production without testing. Slice requires
more system buffers, but reduces process memory usage. more system buffers, but reduces process memory usage.
Do not use slice if there is a lot of short-living connections with no bandwidth Do not use slice if there is a lot of short-living connections with no bandwidth
requirements. requirements.
<p>Use slice only on high-speed connections (e.g. 10GBE), where processor or
bus are bottlenecks.
<p>TCP_NODELAY and slice are not contrary to each over and can be combined on
high-speed connections.