Do not use CGI programs to learn IIS servers

We know that there are a lot of things worth learning about IIS servers. Here, we want to learn how to avoid using CGI programs on IIS servers. First, let's introduce the knowledge of IIS.

The role of the IIS server: the number of website pages that can be opened within the same period of time. Opening a page occupies one iis, and opening a website framework page occupies two to three iis; if images and other stolen links are opened on other websites, images on this site also occupy an iis.

If the parameter is set to 50 iis, 50 pages can be opened at the same time on this site. But in a very short time at the same time) If 50 pages are opened and 50 users need to perform operations at the same time, the probability is relatively low.

Therefore, 100 iis support daily ip1000 simultaneous website access must be far less than 1000 people) is not a big problem, unless the website is leeched or the framework causes other consumption.

When Using CGI programs, the Process must be continuously generated and destroyed, resulting in poor execution efficiency.

Generally, the execution efficiency is as follows:
Static Page): 100
ISAPI: 50
ASP: 10
CGI: 1

In other words, ASP may be 10 times faster than CGI, so using CGI programs can improve the execution efficiency of IIS servers.

In terms of elastic Flexibility): ASP> CGI> ISAPI> Static webpage ). Security): ASP independent) = ISAPI independent) = CGI> ASP not independent) = ISAPI not independent) = Static Web page Static ).

Here we will explain so much about IIS server knowledge.