Gary Stainburn wrote: > Just to put things into perspective here > > 1) I made the comment about the start-up speed. > 2) Although I use PHP frequently my feet are FIRMLY in the Perl camp > 3) Unix Fork/Load/Exec cycle *IS* slow because of the amount of work > involved. The MS equiv will be just as slow > 4) The F/L/E cycle has to be done *every* time the CGI is requested. > > The PHP interpreter is already loaded and therefore *WILL* have a quicker > startup. I don't have figures to back it up, but I would imagine Perl > scripts exec much quicker that PHP asuming both scripts perform the same > function. > > (From memory) Using mod_perl will only require scripts to be loaded and > compiled once per lifetime of the apache daemon so will be much quicker > overall and provide less load on the server than either traditional CGI's.
The question I have is with the current Apache (2.x) and mod_perl (1.27?) involved, when a perl program is incorporated into the httpd process in this manner, how much more *memory* overhead does each httpd process require over related circumstances in php? for example if I use CGI.pm to create a form (using its functional interface to produce the actual HTML seen) and also respond to said form, how much more RAM will each httpd process require if this is run under mod_perl ? One argument I've been handed by the php camp is that in a mod_perl situation, this will cause apache processes to become much larger, thereby taking up more of the precious memory resources. (consider a large gaming website like planetunreal (which IIRC uses .asp), or quakeworld, which garner huge volumes of hits on a daily basis) This issue needs to be addressed firmly to the php camp, because the FUD being spread was enough to cost me one of the most fun hobby projects I was involved with, and the one that got me started on the perl path to begin with while they were still on .asp and had not yet migrated the site to a linux server and mod_php... -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
