[thelist] ASP Limitations

It is not an ASP/ODBC limit, but rather a guide to help plan growth. ODBC
will pool connections to the database so if you are seeing 30+ connections
to your DB I'd check your code (check the links below for direction).

Some of the MS docs I've read (and one of the SiteServer seminars) outline a
40-50 simultaneous connections* per CPU as a guide to determine when you
need to add CPU. Keep in mind this is a sustained 40-50 simultaneous
connections, which means you're getting hit pretty hard.

Win2K, with IIS 5, is better than IIS 4 right outta the box (in the
neighborhood of 25% faster with the default configuration), so that can help
some, also check out the IIS tuning white papers on MS' site to help get IIS
in shape.
<wrap warn>
http://msdn.microsoft.com/workshop/server/feature/tune.asp

http://www.microsoft.com/isn/whitepapers/tuningIIS.asp

http://www.microsoft.com/technet/iis/c06.asp

http://www.microsoft.com/technet/iis/meashd.asp

http://www.microsoft.com/technet/chats/trans/iis908.asp

</wrap warn>

*By simultaneous connections, I mean 40-50 distinct clients requesting an
ASP page at the same time. Note that IIS can handle non-ASP requests at the
same time, and tweaking the request queue, ASP engines cached, ASP pages
cached, and naturally, what those ASP pages do makes a difference.

hope that helps--
sgd
--
think safely

> -----Original Message-----
> From: Chris Garrett [mailto:chris@chrisg.com]
> 
> Does anyone know the limitations of IIS/ASP/ODBC?
> 
> I just heard a worrying rumour that ASP can only handle 30 
> simultanious
> connections per processor! Is this true? I can't figure out 
> if this person