People who manage Internet Information Server (IIS) know that IIS is a simple and troublesome guy. The simple thing is to install it almost no need to spend any brains, choose the path, and then press "Next" all the way to complete; the configuration is relatively simple, as long as there is a certain NT and network knowledge, according to the instructions can set up a model Decent web sites come out. However, managing IIS is not as simple as you might think. After using it for a period of time, administrators often encounter poor server performance. At this time, IIS's performance optimization is on the agenda. The reason
lead to poor performance of the IIS service has two aspects. One is artificial, which means that the administrator did not optimize or configure the error when installing and configuring IIS. The other is objective. With the types of services being run and the number of visitors increasing, the original hardware configuration of the server is no longer sufficient. This requires an increase in hardware configuration.
optimize IIS performance
1.IIS cache on the server configuration is one of the most important items when IIS is optimized to be considered. The server reserves a portion of the memory space for the IIS cache to store objects for future requests so that IIS can retrieve objects from the cache without retrieving them from the hard disk. To adjust the capacity of the IIS cache, you need to modify the registry. The entries are as follows:
\\HKEY_LOCAL_MACHINE
\\System
\\CurrentControlSet
\\Services
\\InetInfo
\\Parameters
\\MemoryCacheSize
MemoryCacheSize ranges from 0 to 4GB, with a default of 3072000 (3MB).
IIS improves system performance by caching system handles, directory listings, and other common data values. This parameter specifies the amount of memory allocated to the cache. If the value is 0, it means "no cache". In this case, the performance of the system may be degraded. If your server network is busy and has enough memory, consider increasing this value. It must be noted that after modifying the registry, a restart is required for the new value to take effect.
2. IIS using the processor so that the longest time. The CPU processor power of the server is always limited. Which application takes up the longest processor and who can get the most performance.
(1) in the NT Control Panel, double-click the System icon.
(2) Click the Performance tab.
(3) under application performance None of the cursor into position, so you can make all the services are running, including the IIS time, processor usage reaches a maximum.
3. Server property settings. There is an option in the server properties that maximizes the total processing power of your web application, and you should of course choose it.
(1) Right click on the Network Neighborhood icon on the desktop and select the Properties option.
(2) Click on "Service Tag".
(3) Click "Server" and then press "Properties".
(4) Select the total processing power to maximize network applications. Then click "OK."
improve hardware configurations to optimize the performance of IIS
when subjected to the above optimized configuration, performance, IIS is still no significant improvement, then maybe you should consider increasing server Configured. However, when it comes to the issue of silver, the bosses will not agree easily unless you use the facts to convince him. You must think clearly about what hardware configuration to improve first. The following are the hardware you need to consider when doing IIS optimization:
Processor: You can upgrade to a faster CPU, and you can add another CPU. But the cost is too high (may change the motherboard or something), the boss is very difficult to accept.
hard disk: hard disk space is NT and IIS services in the following two ways: one is to simply store the data; the other is used as virtual memory. If you use Ultra2 SCSI hard disk, you can significantly improve the performance of IIS.
network interface card: If the server is running on an intranet, you might consider upgrading his card for the 100M card. This is especially effective in situations where network bandwidth is a bottleneck.
Memory: Memory increase to upgrade the system may be the easiest and most effective way. It is also the preferred solution for hardware upgrade recommended by the author. So how do you know that you need to upgrade your hardware? This is related to the use of performance monitors. I will describe it in other articles. Here is a brief introduction: For example, you can use Performance Monitor to track the CPU usage on the server. You can also view the number and frequency of pages that are swapped into memory by the memory. Combine this information with memory usage and other system information to get a system performance report. If this information has consistently shown a high usage rate, then the hardware device should be upgraded.
optimized IIS
precautions in order to avoid future headaches, when you install IIS it should be noted that the optimization of IIS. For example:
1. In order to improve performance and save resources, you should only run the required protocols. Many administrators have not noticed this. I have seen NetBEUI, Tcp/IP and IPX protocols installed on a machine that only serves Web services. Obviously this is unreasonable.
2. The IIS server should be set up as a standalone server, and don't let the server take the extra load required by the domain controller. Imagine: While the server is responding to the user's login, but also providing IIS services, performance can not be reduced?
3. You can distribute the page swap file of the NT server to multiple physical disks. Note that multiple "physical disks" are distributed on multiple partitions and are invalid. Also, do not place the page swap file in the same partition as the WIndows NT boot area.
4. Use disk mirroring or disk stripe sets to improve disk read performance.
5. Regarding the logging of logs, you should use file records instead of logging to ODBC data sources. In addition, the capacity of the memory buffer used to log can be increased during recording to reduce disk activity. The default capacity value for this buffer is 64KB.
6. It is best to store all the data in a separate partition. Then run the Disk Defragmenter regularly to ensure that there are no fragments in the partition where the Web server data is stored. Using NTFS helps reduce fragmentation. I recommend using Norton's Speeddisk to quickly organize NTFS partitions.
7. Although SSL can provide fairly reliable encrypted transmission. But the extra overhead required can cause the IIS server to slow down, especially when dealing with large files. Therefore, SSL encryption should only be performed on directories that do need to be protected.