Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Arkadiy Kulev
Posted to Github: https://github.com/php/php-src/issues/17661 >

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
On Fri, Jan 31, 2025 at 4:06 PM Arkadiy Kulev wrote: > Hi! > > >> This wouldn't really work because FPM does not control the script during execution and would have to check it out after each allocation which is not really viable. >>> >>> Thanks for the feedback! I agree that m

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Arkadiy Kulev
Hi! > This wouldn't really work because FPM does not control the script during >>> execution and would have to check it out after each allocation which is not >>> really viable. >>> >> >>> >> Thanks for the feedback! I agree that monitoring memory usage after each >> allocation would be infeasibl

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
> > > To be honest, I haven't seen a 'slow' memory leak in a long time -- except > when using fgetcsv which has had a reported memory leak since ~2012 > somewhere on the old bug tracker. (I lost the link to it and don't even > remember how to get to the tracker or if it still exists.) I haven't > c

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-31 Thread Jakub Zelenka
Hi, > This wouldn't really work because FPM does not control the script during >> execution and would have to check it out after each allocation which is not >> really viable. >> > > Thanks for the feedback! I agree that monitoring memory usage after each > allocation would be infeasible. However

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-30 Thread Arkadiy Kulev
> > To be honest, I haven't seen a 'slow' memory leak in a long time -- except > when using fgetcsv which has had a reported memory leak since ~2012 > somewhere on the old bug tracker. (I lost the link to it and don't even > remember how to get to the tracker or if it still exists.) I haven't > che

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-30 Thread Rob Landers
On Thu, Jan 30, 2025, at 17:41, Arkadiy Kulev wrote: > Hello! >> This wouldn't really work because FPM does not control the script during >> execution and would have to check it out after each allocation which is not >> really viable. > > Thanks for the feedback! I agree that monitoring memory u

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-30 Thread Arkadiy Kulev
Hello! This wouldn't really work because FPM does not control the script during > execution and would have to check it out after each allocation which is not > really viable. > Thanks for the feedback! I agree that monitoring memory usage after each allocation would be infeasible. However, my sug

Re: [PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-30 Thread Jakub Zelenka
Hi, On Tue, Jan 28, 2025 at 2:17 AM Arkadiy Kulev wrote: > Hello everyone, > > I’d like to propose adding a new configuration directive, tentatively > called *pm.max_memory*, to PHP-FPM. This directive would allow > administrators to specify a per-child memory usage limit, after which the > PHP-

[PHP-DEV] [RFC] Introducing pm.max_memory for PHP-FPM

2025-01-27 Thread Arkadiy Kulev
Hello everyone, I’d like to propose adding a new configuration directive, tentatively called *pm.max_memory*, to PHP-FPM. This directive would allow administrators to specify a per-child memory usage limit, after which the PHP-FPM child process would gracefully exit or restart. Background and Rati