IIS/ASP ok with 500+ Users?

[skeamy]

Ive developed an n-tier application and I am just a few weeks away from it going live. To cut a long story short the only part of the system that I can't really give a good battering to is the front end ASP page. <br>Originally I just installed the option pack and created a project in IIS and put my ASP page into the relevent folder.<br>The system is to run on the Internal intranet so Im not too bothered about security. <br>The ASP page accesses business objects in MTS both through RDS and the Server.CreateObject but I release the instance as soon as Ive done a specific job. For 99% of the time the page will be stateless.<br>The only thing that does persist is a few config strings which are held in the Session object.<br><br>At any one time there could be 500+ instances of this page being run and I really just need to know if the default settings of IIS will cope.<br><br>Any help would be appreciated.<br><br>

 

[Karl Blessing]

well if its IIS4+ then the number of people you can handle , is limited to the bandwidth of your server. (or they're may be a number, but its not as low as 500). so if your server is say a slow 128K ISDN, then I dont think so. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href=

http://kb244.8m.com>

</a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>

http://www.brainbench.com/transcript.jsp?pid=629151

 

[palbano]

I just posted regarding ASP application stressing last week. Go to msdn.microsoft.com and search for 'ASP WCAT'. WCAT is a free IIS application stressing tool designed to provide the answer to the very question you asked.<br><br>Then if you have a performance problem the Visual Studio Anyalyzer can show you where all the processing time is taking place in your application.<br><br>Hope this helps<br>-pete