Quick reminders on how to get mod_perl working with mpm_event. The primary
objective is to never allow mod_perl to garbage collect *any* of your
interpreters during ithread-pool management. Two key components of that
are:
1/ always set PerlInterpMaxSpare == PerlInterpMax.
2/ always set PerlInterpMaxRequests to be at least 10x greater than your
site's daily hit count.
3/ always disable the SetupEnv Option.
Yes, it's that simple. Any other core dumps are due to non-ithread-safe
3rd party Perl modules.
--
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
<joe@sunstarsys.com>
954.253.3732 <//954.253.3732>
objective is to never allow mod_perl to garbage collect *any* of your
interpreters during ithread-pool management. Two key components of that
are:
1/ always set PerlInterpMaxSpare == PerlInterpMax.
2/ always set PerlInterpMaxRequests to be at least 10x greater than your
site's daily hit count.
3/ always disable the SetupEnv Option.
Yes, it's that simple. Any other core dumps are due to non-ithread-safe
3rd party Perl modules.
--
Joe Schaefer, Ph.D.
<https://sunstarsys.com/orion/features>
Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features>
<joe@sunstarsys.com>
954.253.3732 <//954.253.3732>