3 ms·
mod_perl couldn't live safely on shared servers. You had to rent the whole box if you wanted to use mod_perl.
by pnw_hazor 8y ago
mod_perl couldn't live safely on shared servers. You had to rent the whole box if you wanted to use mod_perl.
- nineteen999 8y agoNot even mentioning the memory leakiness of it, it even had a module for tracking leaks: https://perl.apache.org/docs/1.0/guide/performance.html#Memory_leakage https://perl.apache.org/docs/1.0/guide/performance.html#Memo... https://perl.apache.org/docs/1.0/api/Apache/Leak.html https://perl.apache.org/docs/1.0/api/Apache/Leak.html
- feedbeef 8y agoI have a lot of legacy code built on mod_perl that survived over five hardware generations without missing a beat. But mod_perl has become system-cripplingly leaky over the last couple years. I nearly entered a debug rabbit hole before considering a simple workaround. After a quick apache conf edit, mod_perl was swapped out for plain old CGI. Heresy perhaps, but everything is running smoothly again.