On Mon, Mar 15, 2021 at 7:14 AM motoda.hiron...@fujitsu.com
wrote:
>
> > This is working as designed, the server checks only once per second to
> > see if processes need to be started or killed based on the current
> > idle threads.
>
> Is it okay for the number of child processes to fall below
Hi Eric,
Thank you.
> This is working as designed, the server checks only once per second to
> see if processes need to be started or killed based on the current
> idle threads.
Is it okay for the number of child processes to fall below MinSpareThreads in
this environment?
If possible, please
If anyone reads this thread, let's hope they do not interpret those
figures as a valid configuration for a threaded mpm aside from one
used to test a specific behaviour.
El vie, 12 mar 2021 a las 3:54, Eric Covener () escribió:
>
> On Thu, Mar 11, 2021 at 9:29 PM motoda.hiron...@fujitsu.com
>
On Thu, Mar 11, 2021 at 9:29 PM motoda.hiron...@fujitsu.com
wrote:
>
> In the following environment where multiple Listen directives are defined,
> the number of child processes may temporarily fall below MinSpareThreads
> after 6 requests are received at the same time and HTTP request
In the following environment where multiple Listen directives are defined, the
number of child processes may temporarily fall below MinSpareThreads after 6
requests are received at the same time and HTTP request processing is completed.
Is this a bug or a specification?
OS : Red Hat Enterprise
