comment on

I server quite a few CGI scripts from a fairly slow server, and the problem is that although perl scripts will run very fast, it's very slow to create new processes, initialise perl, and load all the modules before my script starts its work.

mod_perl solves this one by having all the modules loaded in advanced, and it's registry modules can cache compiled scripts in memory. But it's rather complicated, and your memory usage can get out of hand if you aren't watching, so I tried FastCGI. It's much simpler.

Rather than loading the script into apache, it creates a process for the script a lot like CGI, but it then just keeps on reusing it rather than discarding it after one use. The other advantage is that using CGI::Fast it's easy to convert your CGI scripts to FastCGI.

So my suggestion is that if you're starting out with Perl is to go with CGI since it's simpler, and you do have room to expand to mod_perl or FastCGI later.

--
integral, resident of freenode's #perl

In reply to Re: cgi or mod_perl by integral
in thread cgi or mod_perl by sberthold

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks