>>As for the network card, we have an ADSL modem serving my site. Don't worry about your server hardware. Befor your server become a bottleneck, you will be restricted by your adsl connection up/down speed.
Regards Leigh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tracey Maule Sent: Tuesday, March 09, 2004 11:06 AM To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] CGI performance > some things to consider : > - use a database? Yep, Firebird > - resource intensive? erm..... > - over ssh? ssl login only > - heavy use of images? no > - mostly static html with small amount of dynamic or vice versa? 50/50? > - apache or iis or optional? Patchy server =) , but I will probably be running IIS for reverse proxy so Apache can serve ASP.NET apps > 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 Yes, I had read that too. Then there was the windows 2000 concurrent users/licensing issue which im still a little confuse about re Apache.... As for the network card, we have an ADSL modem serving my site. > 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 ;) haha ok: a 1cm long peice of string is 1cm long a 1m long peice of string is 1m long how many resources does a 2MB cgi app take? cheers for taking the time to reply ----- Original Message ----- From: "Kurt at DBC" <[EMAIL PROTECTED]> To: "NZ Borland Developers Group - Delphi List" <[EMAIL PROTECTED]> Sent: Tuesday, March 09, 2004 10:45 AM Subject: Re: [DUG] CGI performance > Tracey Maule wrote: > > > 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 > _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
