You can look at Apache::SizeLimit as an alternative - this is designed
to cope with applications which occassionaly "leak memory"..
If one requests uses a lot of memory it will not be recovered -- Perl
doesn't hand this memory back - so subsequent requests are handled by
the inflated process.
Hi again.
I want to correct somewhat what I was saying below, in "Additional hint".
See : http://perl.apache.org/docs/1.0/guide/performance.html#Sharing_Memory
What I was saying about "leaking memory" below remains true.
But even with applications which do not "leak memory" per se, there will a
Additional hint :
Normally, when Apache goes through the "effort" of setting up a new child process, you
would want that this child process then runs for as long as possible (for as many requests
as possible), to avoid the repeated overhead of restarting another child process.
In an Apache pre
Hello David, André,
the server we're working with is fully dedicated to Koha.
Thank you André for your hints about Apache configurations.
@David, same thing, I'll try to preload C4::ILSDI:Services and see if it
helps.
Thanks to both of you, I'll let you know about the results.
Cheers,
Arthur
