Some suggestions for resolving the server is too busy

server| resolution Generally, when your IIS has an error such as "http:1001 Server is too busy", It's because you have too many Server.CreateObject requests in your ASP program, and then every request needs to be queued up until they are actually built.
If your queue has a maximum length of 500, when 499 requests already exist in the queue, then if the NO. 500 request arrives, the "Server is too busy" error occurs.
So how do you minimize the requests that are being applied, and how do you improve response times?
Here are a few suggestions:
1. Use as much as possible. HTM suffix file, avoid using. ASP (especially when special events are likely to be a condition of overload). Because the HTM does not plug the server at the same time can get maximum cache performance. (I have introduced an article on the efficiency of this issue, in the essence of the area)
2. Try to use less server.createobject in your ASP
3. Strictly limit your ASP calls to external resources that are not on your server, such as your resources on another server
4. Try to optimize your network performance and stability, such as enhancing your background SQL Server database or remote file sharing LAN performance.
5. Try to make each component fast and call it speed. For example, if a component is called 20 times a second, it must be completed in 1/20 seconds or the component will block. You know, a blocked component will cause all the ASP crashes on your site
6. Monitor the performance status of your site every week, because a single object that can cause a blockage can have a bad effect on your entire site.