On Thu, May 27, 2021 at 7:41 AM Marc Serra <mse...@manxa.com> wrote: > Thank's Eric, I understand. > > But if configuring a load balancer I'm adding another hop with reducing > the performance, seems that is not the best way to improve this > performance, correct? > > As I explained before, it's only a test setup before move to a real > environment. > > Now I have a single server (8 cores, 32GB RAM with prefork) and the > following apache tunning. In some moments, I have thousands of concurrent > connections that collapse the server and I thought the best way to fix this > was by setting up a load balancer. Isn't it? > > ServerLimit 800 > StartServers 10 > MinSpareServers 200 > MaxSpareServers 400 > MaxRequestsWorkers 800 > MaxConnectionsPerChild 10000 >
"load balancer" is an overloaded term. A HTTP reverse proxy is one way to scale to multiple servers. There are ways that are lighter weight at runtime like a VIP or NAT forwarding. But it may be moot for your real workload.
