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.
| [reply] |
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?
| [reply] |