I have a very large ASP.NET web application that was recently upgraded from 1.1 to 3.5 framework. This has NOT hit production yet because I am still having performance problems.
One thing I am noticing is the number of "connections" on the application servers. (Test environment has 4 servers running Microsoft's NLB, Network Load Balance, while the production environment is running 8 application servers).
In production (which is still .NET 1.1) each server's # of connections doesn't get higher than 50, usually averages around 25 to 35.
In test (.NET 3.5), I had a "load test" last Friday and also Tuesday of this week and both times I have seen the # of connections on the [4] application servers get as high as 450, and is commonly between 100 and 300.
Also, in production, I average 1000 active users, and for the load test I had 500.
This is a HUGE difference between the environments/frameworks.
For the upgrade process, the code was only changed in order to get it to compile, NO CHANGES except for 1 class. That one class that had to be reworked was the XslTransform (1.1) changed to XslCompiledTransform (3.5). That whole class changed pretty drastically in their upgrade.
Do any of you architects/ASP pros/IIS pros know of any big changes that could be causing my issue? Is there some setting that I could change in a web.config or IIS website property that is new and needed for .NET 3.5?
Any help would be greatly appreciated! Thanks!
One thing I am noticing is the number of "connections" on the application servers. (Test environment has 4 servers running Microsoft's NLB, Network Load Balance, while the production environment is running 8 application servers).
In production (which is still .NET 1.1) each server's # of connections doesn't get higher than 50, usually averages around 25 to 35.
In test (.NET 3.5), I had a "load test" last Friday and also Tuesday of this week and both times I have seen the # of connections on the [4] application servers get as high as 450, and is commonly between 100 and 300.
Also, in production, I average 1000 active users, and for the load test I had 500.
This is a HUGE difference between the environments/frameworks.
For the upgrade process, the code was only changed in order to get it to compile, NO CHANGES except for 1 class. That one class that had to be reworked was the XslTransform (1.1) changed to XslCompiledTransform (3.5). That whole class changed pretty drastically in their upgrade.
Do any of you architects/ASP pros/IIS pros know of any big changes that could be causing my issue? Is there some setting that I could change in a web.config or IIS website property that is new and needed for .NET 3.5?
Any help would be greatly appreciated! Thanks!
