in reply to perl cgi shared hosting memory limit problem
#define FLAME ON ... :-D
First, you have to find a hosting company that doesn’t presume that the letter “P” in “Perl” doesn’t stand for “PHP.” (Tip: if they spell it PERL, i.e. uppercase-only, run like hell ...)
I had a site running for many years on (Omitted) without trouble, even though their Perl was ancient. But one day it “unexpectedly” just stopped working, and when I logged-in to check it, the ulimit was set so small that the cpan command wouldn’t run! (Fortunately, cpanm still did.) The number of Apache-workers running on that ridiculously-tiny VM was ridiculously-large, and I am quite sure that every site except mine was running PHP. (They had a Big Phat PHP with all the options turned-on.) So, I loaded-up my site and moved it to a much nicer home. They never bothered to announce any of the changes that they had obviously been making over time.
Mind you, it’s not that I have anything against PHP, because I don’t. (“If it on-ly had a brain ...”) ;-) But, shared hosting companies know which side their bread is buttered-on, and they squeeze a server until it hurts.