Performance testing of IIS and ASP. NET with requests per second

I recently conducted a performance test on IIS. I have a deep understanding and published the data for your reference.

The server bandwidth is 1950 mbps for Dell 2003, windows, and Shanghai Telecom IDCs.

Test method:

1. Develop a flash. Flash regularly (for example, 1 second) requests a page such as show. aspx.

Note: Flash has security restrictions: Show. aspx must be the same domain name as the flash download server. If the host name is different, you also need to add a crossdomain. XML in the web root directory of the server where the show. ASPX page is located, see http://kb.adobe.com/selfservice/viewContent.do? Externalid = tn_14213

2. Talk about cooperation with a website with large traffic and embed your own flash on the webpage.
Note: Flash needs its own server.

3. Observe the performance of IIS on dynamic pages:

IIS: keepalive
Number of requests: 7679 requests/second
CPU: 100%. [If an ASP. NET cache is added for one second, the CPU usage drops to 70%]
Bandwidth: 70 m/100 m [telecom data center can reach 70 m, real Internet bandwidth, It's good]

TCP Connection Established = 14298
TCP active = 149

The number of different IP addresses at the same time: about 1-2 K.

4. Show. aspx:

A small XML file is returned for flash parsing.

 
5. How to Write flash:
 
Anyone who finds an artist should write it.

6. highlights:

We put the server behind the netscreen firewall. IIS prohibits keepalive. After a few seconds, the firewall CPU turns yellow, and the system processing capability decreases to 2000/second. Directly place the bare metal server on the Internet. IIS prohibits keepalive, and the system can process 6000 times/second.