in reply to Webhosts: What are reasonable resource limits for Perl?

I thought this was a little restrictive. I was curious to know what sort resources limits other monks had seen on virtual web hosting providers and what they thought was "reasonable".

I've seen similar restrictions (2 CPU seconds or 15-20 clock seconds). In my opinion, when you are on a shared system with a typical $25-$50/month account, those limits are quite reasonable. They help ensure a minimal level of service to others on the box.

If you're doing something with a CGI that takes more than 2 CPU seconds, and have already carefully considered your algorithms and partial-result caching, you ought to consider getting onto your own box, if only out of fairness to others.

My opinion. YMMV.

  • Comment on Re: Webhosts: What are reasonable resource limits for Perl?

Replies are listed 'Best First'.
Re: Re: Webhosts: What are reasonable resource limits for Perl?
by Davious (Sexton) on Jan 21, 2002 at 06:49 UTC
    So I guess with those types of web hosts running a script that might exceed those limits (eg: newsletter mailer, http link checker, etc) just isn't an option?
[reply]
      So I guess with those types of web hosts running a script that might exceed those limits (eg: newsletter mailer, http link checker, etc) just isn't an option?

      Many ISPs distinguish (and put separate restrictions on) cron jobs. My ISP allows cron jobs for certain types of accounts, and recommends (or perhaps insists -- I'll need to check) that the jobs run nice'd. I do stuff like link checking and log analysis at nice -20 at an off-hour.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom