Hello all
*without starting a discussion on whether CGI apps are a good idea*
They are ;)
Could someone point me in the right direction to find out hardware requirements vs user numbers?
Yeah, I'll tell you the hardware to support a number of users of your cgi app if you tell me how long a piece of string is ;)
some things to consider : - use a database? - resource intensive? - over ssh? - heavy use of images? - mostly static html with small amount of dynamic or vice versa? - apache or iis or optional?
*BUT*
2 things :
1) - CGI is a very good starting point. You will find out a lot
about your application before the speed of cgi gets to be an issue.b) - Hardware has very little effect on the speed of web serving
(cue lots of 'I use a 486 as a router' stories), other than
quality hardware is more valuable. Get a quality network card,
apart from that the first thing you'll do hardware wise is
replace a power supply or a hard drive.Actually, because OS's are getting trickier with filesystem and app caching mean, cgi isn't losing ground as quickly as it has been. And the cgi server-model is *sweet*. If anything happens it just dies, frees all its resources and waits for someone to start it up again. Probably the worst property of cgi is that you don't have fine grained - object level - caching that other layouts give you. That probably hurts more than the cgi start up time now. (Also remember that slow cgi is very very fast).
Cheers, Kurt. _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
