Load Balancing in ASP

Easiest solution would be just to have a big really fancy server.  As for load balancing with ASP I'm not really sure how.  As long as your code is efficiently written and the server is good enough there shouldn't be any problems.  The things I think help with optimisation most in ASP are:

1)  Most important thing is to always remember to close connections and drop objects after use, otherwise they hang around in memory and the server can crash/slow down a lot.

2)  When looping through large sets of data, use rs.getRows.  Speeds up some pages by 5 seconds.  Good practise to use as much as you can

3) Debugger, make sure Option Explicit is on each page.  Also you would probably want the buffer set so that it processes the page before feeding anything out.

4)  ASP breaks (as in the <% and %>) slow down code a bit.

ASP optimisation has been written about extensivly, check google for more tips.

Most load balancing is done through network "appliances" - hardware that communicates with an agent on the server that's monitoring performance. The network hardware then routes requests to the least busy server and monitors session state so all requests for that session go to the same server. Often you have to include additional session handling code though just in case the hardware screws up a session.

A simple solution would be 2+ Servers, installed with Windows Server 2003 Enterprise Edition and enable load balancing with failover. Then you essentially have a IIS Server Farm and you need to make sure how you code your asp trying to avoid session object because they may get lost when one user fails over to another server. If you use asp.net you can confiure a Session Server where session information is saved on a SQL Server or a dedicated Session Server Application thus I don't think you can do something like this with classic asp. There is plenty information on how to implement a solution like that on technet @microsoft.com