|
Hi Nigel, Thank you for prompt reply. The apache version we are using is : Apache/2.4.10 (Debian) Are you having any idea, whether the below memory leak issue is resolved in any of the latest releases of apache? Thanks Arnav
From: Nigel B. Peck [mailto:nigelbpeck@xxxxxxxxx]
On Thu, 22 Aug 2019 at 12:02 am, Arnav Garg <arnav.garg@xxxxxxxxxxxxx> wrote:
It specifies the number of connections that a child process will serve before being closed and a new one spawned. Having it as 0 means there’s no limit so they just keep running. I’m suggesting 100 because it seems you have a memory leak, so looking to make sure they are restarted before that takes up too much memory. The cost is the overhead of spawning a new process every X number of connections. If you set it higher then your memory leak will have more effect. Best thing is to set it and then monitor and load test the server to get data to guide decisions on what works for your situation. And identify and fix the memory leak :) Hope that helps. Nigel Web Technologies and Linux Admin Mentor The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECTI or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECTI or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. |
|