On 15 Mar 2003 at 8:52, zentara wrote: > On Fri, 14 Mar 2003 10:47:52 -0500, [EMAIL PROTECTED] (Brian > Jefferies) wrote: > > > Is there a general consensus regarding compiling perl into binary > >executable? > > > > > >I love perl, but I don't understand the sense in re-compiling the same cgi > >script (for example) 10,000 times a day. > > > >I have read and tested "perlcc -b" and found no performance improvement over > >running the .pl. > > Get the fastcgi module. It works on almost any script. It compiles the > script once, and keeps a copy in memory. You can set different > configurations for different scripts(like how many spare copies to > keep). Some can be fastcgi, and others not. Some can be dynamic(fresh > cgi for each call) or static(reuse same cgi, with problems of variables > overlapping). > > It's alot easier to use than mod_perl. > > If you need a similar function, but not cgi, try the PersistentPerl > module. It does similar things, but on plain perl scripts run locally. > If you are interested in having a tool for a multitude of Apache issues, in addition to fast cgi execution, I would recommend mod_perl. Setting up fast cgi (via the mod_perl Apache::Registry) is easy; the 'good' parts of mod_perl do require a lot of study and practice, but IMHO are well worth it. See perl.apache.org.
Aloha => Beau; -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
