Difference between IIS 6.0 and IIS 7.0 Part 1 of 2

Performance

A good metric listed below is the “efficiency” or “cost” of the number of requests per CPU cycle (RPS / CPU Utilization %).  Using this metric, IIS 7.0/W2K8 RTM is over 10% more efficient then IIS 6.0/WS03 SP2in handling live web platform traffic for the site

Listed below the graphical data results is the methodology used in this performance analysis.

Server Efficiency (RPS/ CPU %) – Efficiency of serving live web platform traffic

W2K3 SP2     4.36   “requests per CPU cycle”

W2K8 RTM   4.84   ~ 10.9% increased efficiency

CPU Utilization (%)

W2K3 SP2     44.8%

W2K8 RTM   52.8%   ~ 17.9% degradation (This is impacted by the increased RPS the W2K8 servers are handling)

Web Service – Total Methods Requests/Sec (RPS)

W2K3 SP2     194

W2K8 RTM    255   ~ 31.4% more traffic is being sent to the W2K8 RTM servers

Web Service – Current Connections

W2K3 SP2     280

W2K8 RTM   294   ~ 5% increase

 Load Balancing – Current Client Connections

W2K3 SP2     116

W2K8 RTM   116   Equal – as the hardware load balancer maintains the same amount of outstanding open client connections.

.NET CLR Memory – % Time in GC

W2K3 SP2    1.1%

W2K8 RTM   2.5%  No significant degradation in “Time in GC”

Performance Overview and methodology:

Site: www.microsoft.com 

During this assessment the live www.microsoft.com site was comprised on 80 servers.  There were four load balanced clusters of twenty servers each, located in multiple datacenters.  This performance analysis was developed by using a single twenty server cluster on the www.microsoft.com site.  The cluster is comprised of 19 Windows Server 2008 RTM servers (W2K8 RTM) and a single Windows Server 2003 SP2 (W2K3 SP2) server all taking live internet facing traffic.  This Lone Windows Server 2003 has become quite famous.  In fact, he actually has his own blog located at http://blogs.technet.com/windowsserver/pages/about-lone-server.aspx

Hardware:

  Model: HP DL585 G1 (4 dual-core CPUs)

  RAM: 32GB 

AppPool Mode’s in IIS 7.0

·         Integrated mode[ASp.NET]

·         Classic .NET AppPool

In Previous versions of IIS, the Session of ASP wasnt accessible to ASP.nET. the reason behind in IIS 6 there were two different ISAP dlls[aspnet_ISAPI.dll and asp.dll] for ASP and ASP.NET so they couldnt share the Session and Application objects

Solution : was we can force the asp extension to use ASP.NET handler in IIS 6.0

This is default feature in  IIS 7.0, which is known as Integrated mode

Migrating the Application Configuration
If you simply move the application to IIS7.0 server. it runs this below command.

if you want to disable and not have to run the application
add this to application web.config file
<system.webServer>
<validation validateIntegratedModeConfiguration=”false” />   
</system.webServer

Command to run the ASP.NET application under IIS 7.0 Integration mode

%windir%\system32\inetsrv\APPCMD.EXE migrate config <Application Path>

Where <Application Path> is the virtual path of the application containing the site name, such as “Default Web Site/app1″.

Moving Back to Classic ASP.NET integration Mode

configure your application pool to run under Classic mode

Selecting ASP.NET Version for an Application

ASP.NET v1.1 application on /app1:
ASP.NET v2.0 application on /app2:’

Unfortunately, due to the limitation of the ability to load only one CLR version into a single worker process

Taking Advantage of Integrated ASP.NET Mode
Your ASP.NET application should be using those components which make use of this feature.