https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32558 --- Comment #12 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to Kyle M Hall from comment #11)
(In reply to Jonathan Druart from comment #9)
(In reply to Jonathan Druart from comment #8)
The first argument could be the memory footprint, but with bug 28413 it should not be a problem.
And just noticed that it's broken, see bug 32561.
I had another thought triggered by bug 32561. Your solution on that bug only keeps the memory footprint down until the first time that the require for Koha::Plugins is evaluated. At that time the memory usage will jump back up and remain there. With this patch, those inflated processes will go away after processing that job. I think both techniques should be implemented for maximum flexibility. For example, someone may want to deploy a fast queue with 20 max processes, and a slow queue with 10 max processes.
Just remembered that the process forks, so I think my memory concern is invalid. I do think the rest of my comment stands though ;) -- You are receiving this mail because: You are watching all bug changes.