mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-28 00:33:19 +00:00
DOC: fix a few spelling mistakes
This commit is contained in:
parent
6ad6bde9e1
commit
cc123c66c2
@ -1307,7 +1307,7 @@ persistent connections per user).
|
||||
|
||||
Even if you disable keep-alive, if the server takes a long time to respond,
|
||||
you still have a high risk of multiple users clicking at the same time and
|
||||
having their requests unserved because of server saturation. To workaround
|
||||
having their requests unserved because of server saturation. To walk around
|
||||
the problem, you increase the concurrent connection limit on the servers,
|
||||
but their performance stalls under higher loads.
|
||||
|
||||
|
@ -755,7 +755,7 @@ one first layer running on multiple processes and in charge for the heavy
|
||||
processing, passing the traffic to a second layer running in a single process.
|
||||
This mechanism is suited to SSL and compression which are the two CPU-heavy
|
||||
features. Instances can easily be chained over UNIX sockets (which are cheaper
|
||||
than TCP sockets and which do not waste ports), adn the proxy protocol which is
|
||||
than TCP sockets and which do not waste ports), and the proxy protocol which is
|
||||
useful to pass client information to the next stage. When doing so, it is
|
||||
generally a good idea to bind all the single-process tasks to process number 1
|
||||
and extra tasks to next processes, as this will make it easier to generate
|
||||
|
Loading…
Reference in New Issue
Block a user