New Features of Microsoft IIS 8: CPU and SSL

Every version of Microsoft Internet Information Service (IIS) is like a part of the novel series. This novel is published several years ago, but it proves to be worth waiting.

IIS8 will be released with the beta version of Windows Server 8. IIS8's new feature aims to bring together large-scale Web servers. However, a good result of all functions is how to allocate smaller servers or even separate servers.

Directory

• CPU throttling: Next Generation
• SSL Improvement
• Restrictions on FTP logon and dynamic IP addresses
• Multi-core scalability and NUMA sensing
• Webpage Interface
• Conclusion

CPU throttling: Next Generation

IIS7 has the CPU throttling function to prevent irregular websites from occupying too much CPU. Unfortunately, IIS7 is too desperate, which makes it less useful than imagined.

First, when you want to set the website's throttling, the only effective method is to end all the processes of the website within a period of time. You can set the CPU threshold and duration, but this means that the website is completely paralyzed during this time. There is no way to allow a site to configure IIS at any time and use only 90% of the CPU processor X (or all processors.

The CPU throttling feature of IIS 7 is desperate: you either stop the process or do not take any action

Second, IIS 7's CPU Throttling is bound to a given application pool. If each website has a separate pool, This is not bad. If you place the CPU core in this way, you can. Even for Single-core websites with low CPU usage .) However, if you have multiple websites that share the same application pool, once the CPU consumption of one of the websites fails, all the websites will be disconnected.

To solve all the above problems, IIS 8 adds two new actions in the CPU throttling work project:

Throttle and Throttle under load, Throttle controls the CPU of a given worker process and any sub-processes generated by this process. Throttle allows the website to use as many CPUs as possible, but if the process competes with other processes for CPU usage, Throttle will Throttle the process.

In this way, throttling can be implemented without shutting down all processes, and flexibility is increased in multi-user environments. You can run multiple websites in parallel, whether or not to set a clear processor relationship for their work processes, without affecting each other.

Another new feature of IIS 8 is the application initialization module, which allows a site to receive page requests and respond to friendly messages, and the website code is still accelerated. This function prevents users from clicking the refresh button on the browser when they re-edit the favorites folder.

SSL Improvement

I have never liked how IIS processes SSL. "Clumsy" and "troublesome" are two of the least harsh adjectives I have used to describe the process of adding and managing SSL certificates in IIS. Fortunately, three major new improvements have been made in SSL processing of IIS 8.

• Centralized certificate management. IIS 7 forces you to enter the corresponding certificate in each IIS instance. If you are managing the server resources of the entire company, this is a headache. IIS 8 can help you create a core certificate storage area (CCS. In this way, all company-authorized certificates can be stored in a separate location. The certificate file name can be used to automatically map and bind the certificate to the domain. In this way, you can also create certificates for multiple domains. Just copy the certificate multiple times and rename it)
• Server Name Recognition is supported. Not long ago I found it difficult and painful to install SSI on the server when multiple websites share an IP address and all use the host title. A new technology called server name recognition allows SSI to be used on websites that can only be accessed through host titles, but it also requires support from servers and clients. IIS 8 fixes the equation on the "server" side. Recently, Some browsers support this function.
• Scalability. As the certificate loading and management methods are improved, websites that support SSL are more efficient in measurement, you can run more certificates on the same hardware to hundreds of certificates ). You must also note that the configuration file (*. config) processed by IIS has been re-created to the same mode.