in reply to Re: Question on Web Server Usage and Perl
in thread Question on Web Server Usage and Perl

thank you for your response. Ive been told by others that ActivePerl's ISAPI extension is my best bet. Maybe Im just inexperienced and uneducated with web server technology. But seems like 4 AMD 64 chips is alot to have to meet those requests. I was think no more then 2 AMD chips ( and not 64 ) with 2GB of ram and a few SCSI OR SATA drives. But Im no system engineer either. Thaks for your reply. I asked the terminate questio because Ive seen snippets implying that perl processes may "hang around" longer then they should.
  • Comment on Re^2: Question on Web Server Usage and Perl

Replies are listed 'Best First'.
Re^3: Question on Web Server Usage and Perl
by dorward (Curate) on Nov 26, 2005 at 07:37 UTC

    seems like 4 AMD 64 chips is alot to have to meet those requests

    That was a system spec I plucked from thin air, simply to provide contrast with the lower end spec. I don't know how much system resources it would take to handle that many requests with CGI. I wouldn't handle it with CGI myself, nor would I use Windows for it, and it would also depend on what the scripts actually did. A script that generates a complex 1600 by 1200 pixel fractal image as an image/png based on user input is going to demand more resources then one which just prints "Hello, world".

    I asked the terminate questio because Ive seen snippets implying that perl processes may "hang around" longer then they should.

    When running under mod_perl, and presumably ISAPI, Perl processes (well, the Perl process is wrapped up inside the Apache process) do hang around once the script has finished executing - then they can be reused for the next request that comes in.

      Thanks for the response. Understood that the scenario you gave was just an example. Wanted to be sure that you were not implying something I should be aware of. I DONT want to use CGI. I DONT want to use IIS. Im stuck using IIS 6. Checked out ActiveState. They had a module called PerlEx that is not supported anymore. Im trying to find out if there PerlIS.dll is the recommended solution to use. Supposedly PerlEx was 2 to 48 time faster then PerlIS ( by activstates docs ) I understand also that differenct apps have different needs. Just for grins what would use if NOT CGI? Is FastCGI REALLY a better solution?