Some of the previously collected information---how to resolve some of the recommendations of the "Server is too busy" issue

Some suggestions for resolving the server is too busy
Generally, when your IIS takes place such as "http:1001 Server is too busy"
Error is due to an excessive number of Server.CreateObject requests in your ASP program
, and then each request needs to wait in line until they are actually built.
If your queue has a maximum length of 500, when there are 499 requests in the queue,
At this point, 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 in those who are likely to recruit
Overload of the condition when special event occurs). Because HTM does not plug the server and can get the 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, a component is called 20 times a second,
Then it must be done in 1/20 seconds, or the component will block. You know, a blocked
Component will cause all ASP crashes on your site
6. Monitor the performance status of your site every week. Because a single object that can create blocking can generate a whole web site
Very bad influence.