Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
> When Webware is not being used, it would presumably get swapped out to disk
> by the O.S. not given much priority. As it gets used, it would be swapped
> back in, which seems no worse than launching a CGI.
That's a good point.
> Consider that for *every request* CGI will incur this additional overhead:
>
> * Launch a process
> * Load the interpreter (python)
> * Load the standard modules (os, sys, etc.)
> * Load commonly used modules (MySQLdb, DateTime, etc.)
> * Load the script (MyPage.py)
> * Other initialization (e.g., opening a database connection)
> * Shutdown the process
>
> How many requests would it take for Webware to show a worthwhile gain over
> CGI? I'm guessing not too many.
Well, that's if you are doing Python CGI for every page. This is
poorly supported on most hosts anyway. Typically people either have a
small set of Python (or usually Perl) CGI scripts, or else they have a
bunch of PHP or ASP files. If you have a database driven site, you
would probably do best to use PHP or ASP.
> >A typical site constructed with CGI -- where there are a few portions
> >that are dynamic, and more portions that are static -- will probably
> >use less resources over time. This is what most shared hosts are
>
> Not sure what you are implying about the "more portions are static". Even
> if the CGI spews forth HTML pieces that are fairly static, all the overhead
> I list above still takes place. The only static pieces that avoid that are
> things you like to like images, stylesheets and JavaScript. Which in both
> cases should be cached by the browser.
Many CGI-based websites only have CGI pages for specific parts of the
page. They may generate the pages on a schedule, but just serve .html
files.
This is what hosts seem to encourage. The cgi-bin directory certainly
is meant to support this sort of use. Though there are a number of
websites who are nearly entirely served off of cgi-bin.
I'm under the impression that PHP is already persistent in many ways.
Ian
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
