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

High load documentation update

Browse Source
This commit is contained in:
z3APA3A 2017-10-08 23:20:52 +03:00
parent 2fd9f945c8
commit 695bfc89ac
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

@ -64,8 +64,9 @@ number of outgoing connections above this limit, extending ephemeral port range
is not enough, you need additional actions: is not enough, you need additional actions:
<ol> <ol>
<li> Configure multiple outgoing IPs <li> Configure multiple outgoing IPs
<li> Make sure 3proxy is configured to use different outgoing IP by either using <li> Make sure 3proxy is configured to use different outgoing IP by either setting
multiple services with different external interfaces external IP via RADIUS, or by using multiple services with different external
interfaces, example:
<pre> <pre>
allow user1,user11,user111 allow user1,user11,user111
proxy -p1001 -e1.1.1.1 proxy -p1001 -e1.1.1.1
@ -151,6 +152,9 @@ There are known race condition issues in Linux / glibc resolver. The probability
of race condition arises under configuration with IPv6, large number of interfaces of race condition arises under configuration with IPv6, large number of interfaces
or IP addresses or resolvers configured. In this case, install local recursor and or IP addresses or resolvers configured. In this case, install local recursor and
use 3proxy built-in resolver (nserver / nscache / nscache6). use 3proxy built-in resolver (nserver / nscache / nscache6).
<h4>Do not use public resolvers</h4>
Public resolvers like ones from Google have ratelimits. For large number of
requests install local caching recursor (ISC bind named, PowerDNS recursor, etc).
<h4>Avoid large lists</h4> <h4>Avoid large lists</h4>
Currently, 3proxy is not optimized to use large ACLs, user lists, etc. All lists Currently, 3proxy is not optimized to use large ACLs, user lists, etc. All lists
are processed lineary. In devel version you can use RADIUS authentication to avoid are processed lineary. In devel version you can use RADIUS authentication to avoid