We have recently moved the bulk of our legacy systems from the old CSLA v1 to the latest version of the code base. All is great :) but i have significant performance issues when i deploy our dataportals to a windows 2008 server running iis 6. The exact same code and deployement method running on an older server running iis 5 with less cpu power and resources is running much faster.
The kind of difference i am seeing are along the lines of:
Starting the application, time to get to the front screen of the app from application start-up:
on IIS 5 -- approx. 3.5 seconds
on IIS 6 -- not sure, about 4 minutes, long enough to boil the kettle anyhow
I do not claim to be a pro at setting up IIS 6, so was hoping someone out there may be able to give me some suggestions. At present IIS 6 is running pretty much with its defaults, the applications are all large C# back office systems using the CSLA as the data tier under IIS on a remote server. A relatively small number of client machine's, approx 90. But the speeds above are with just my machine on the system.
So then, anyone know of any magic switch?
Senior Software Architect
Yeah, it is i guess an unusual setup but as IIS7 is/was not approved at the time of the machine being setup my it team installed IIS6 rather than leaving 7 on the 2008 box. Maybe this is a cause for concern :S
Thanks for the pointers guys.
I got to the bottom of the problem, probably a dumb ass mistake lol, but i had Windows Authentication set to false where i needed it to be set to true. All is sorted now :)
Ok thanks, i will check into the networking side of things.
Whilst the app is starting the CPU is cycling at 100% on the worker process for the duration of start-up. Have no idea why, the usage on the IIS5 install barely registers on the cpu monitor.
Copyright (c) Marimer LLC