Unreasonable configuration of Apache in WDCP

<IfModule mpm_prefork_module> LIS)(?X<]? StartServers 5 6DM$g=/'? MinSpareServers 5 -9%:i?lX?~ MaxSpareServers 10 N^#?Z?JoR MaxClients 150 X>d"?]G??D MaxRequestsPerChild 0 ?$:cE ^8?K </IfModule> hU???(umL< /,?8?9p&?h The unreasonable place lies in MaxClients and MaxRequestsPerChild. ?_a5?d?Q9Z 7R`M,u~f2^ MaxClients specifies the maximum number of APACHE processes that can be started. For small memory hosts, this setting (150) can easily run out of memory. I ?CZ4 A{I MaxRequestsPerChild specifies the maximum number of requests that each APACHE process can process. After the number of times, the process will exit and then restart the new process. The significance of this is that the process will have a memory leak, that is, the process. The memory used will be more and more, more and more, more and more, more and more, can not be released. After setting MaxRequestsPerChild, the process restart can be solved. The WDCP is set to 0, 0 means Never quit. Te.Y#lC T$ yL%K?4?$?z A screenshot of the WDCP example is as follows: ??^M3?~^lV

Image: 1111.png
r?#+d?&?.|  25 APACHE processes occupying 755M of memory. <A??[E:*`* M9Cv ?wMi Send another example of LNAMP (http://www.server110.com/lnamp/) for comparison: ?u?\\E?Y[?1

Image: Untitled.png
LUG; (Fko 13 APACHE processes, occupying 47M memory.