Shulou(Shulou.com)05/31 Report--

This article shows you how to achieve Windows Server 2008 R2 website service performance comparison, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

WebBench tests the performance of the server as a WebServer. We install IIS components on the server under test to provide Web services for testing. In the test, we use 60 clients in the network lab, configure 120 test engines, and test the server with WebBench6.0 's built-in dynamic CGI and static page script respectively.

Network laboratory console

The static test is that the client reads the Web page (wbtree) pre-placed under the server WebServer. This test mainly examines the performance of the server disk system and network connection. We used 56 clients in the lab to send requests to the server under test in conjunction with Static_mt.tst multithreaded static script testing.

Dynamic testing focuses on the performance testing of the server CPU subsystem, which provides sufficient load for the Web server. We compile a CGI source file Simcigi.c written in C language into Simcgi.exe and use it as a CGI script in dynamic testing. During the testing, each PC installed with WebBench client software will continuously send CGI requests to the server within 300 seconds, while the console will record and summarize the data of the server's response to CGI requests. The score of CGI test mainly depends on the performance of server processor subsystem. The processor subsystem includes CPU, memory and memory controller. CPU frequency, cache, memory capacity and memory bandwidth all affect this performance.

Test platform

We use a DELLPE2900III server in the evaluation center, which is equipped with two-way Intel45nmXeonE5430 processors at 2.66GHz frequency, and can support SSE4.1 instruction sets. The server also uses an Intel5000X chipset to provide 24MB's SnoopFilter cache, which can improve memory / processor performance under heavy loads. In order to avoid the bottleneck of the disk subsystem, we used 8 Cheetah25K.5 of 15000RPM to build a RAID0 array through a LSIMegaRAIDSAS8408E of PCIex8 interface. It can provide sufficient bandwidth.

Finally, the network subsystem uses two Broadcom BCM5708C gigabit network cards on the DELLPE2900III board, and uses the maximum driver of Broadcom 12.26.02 and uses BroadcomBACS3.0 to build a network card Team. BCM5708C is a landmark Broadcom gigabit network card product that supports RSS receivers with up to eight queues to scale queues, distribute network load to eight processor cores for parallel processing, make full use of multi-core processors and improve network throughput.

The two generations of operating systems carry different versions of IIS (InternetInformationServer), with 2008 with IIS7.0 and 2008R2 with IIS7.5. The 2003 carries IIS6.0.

IIS 6.0 vs IIS 7.0

IIS 7.5

WebBench testing performance

As a result, we found that the dynamic page performance of WindowsServer2008R2/IIS7.5 was a little higher than that of WindowsServer2008/IIS7.0, * reached 5724Rps, while the peak value of 2008 was about 10% higher than that of 5181 and 2008R2. The performance of static pages is still being debugged (probably related to drivers) because the results are strange.

From the point of view of the reason, the author thinks that the relationship between IIS is not very great, and the factors that cause the promotion should be the same as those in NetBench, the most important are two aspects: the system kernel and the network subsystem. The interrupt processing of WindowsServer2003 can only be carried out on * physical CPU cores. This core quickly became a bottleneck in servers with a large number of IO (and therefore a large number of interrupts). In WindowsServer2008, interrupt handling (ISR and DPC) can occur on multiple CPU cores. On the other hand, WindowsServer2008R2 has improved the processing of DPC.

As for the improvement of the network subsystem, each generation of Windows will improve its NDIS (NetworkDriverInterfaceSpecification), WindowsServer2003 is 5.2, 2008 is 6.10, and 2008R2 is 6.20. Compared with NDIS5.x/6.0,WindowsServer2008 's NDIS6.1, it supports RSS (receiver extension) and MSI-X (extended message notifies interrupt) better, and supports packet header and data processing independently. WindowsServer2008R2's NDIS6.20 makes further improvements to RSS. However, the drivers we used in the 2008/2008R2 test are based on the NDIS6.0 architecture, so in the end, there is not much difference between the two operating systems.

The above content is how to achieve Windows Server 2008 R2 website service performance comparison, have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.