IIS6 Disappointing - VERY slow for ASP pages

If you think it's authentication, you should be able to:
1. Look at the property page for the vdir/app and determine if any
authentication is even enabled
2. Look at the IIS Web logs for the website in question because
authentication negotiation would usually show up as extra
requests/responses.
3. Use NetMon (included in WS03 Add/Remove Windows Components) between two
separate machines to sniff all traffic of the request/response

#3 will definitively tell you throughout the whole "slow" request:
1. What request exchanges have happened prior to that slow request
2. What request is actually slow
3. How long all the request/response took

I also notice a lot of people complaining about perf as well, but you must
realize it's not a trivial problem to solve. There is no magic "Make it run
faster" wand.

We've improved ASP performance/scalability in many ways (you won't find this
out until you get a 2P, 4P, or 8P box -- you will quickly find that IIS5
does not scale at all while IIS6 will scale up the HW with you). We've also
made ASP scale and perform much faster with UNC-based content on IIS6.
However, you won't see any of this improvement unless your own code is also
scalable to take advantage of the improvements. Performance is pinned by
the weakest link.

My personal suspicion is that when you're talking about performance, you
need to be absolutely certain of the configuration of the system under test.
Some setting (or combination of settings) may be the performance culprit
under some scenarios, but we won't know what they all are. I can say that
the IIS perf testing is done under very strict configurations (for
reproducibility) so that we can scientifically compare results. Real-life
tuning is difficult at best since users rarely even know how to control
their system configuration.

Making a comparison like "The same application runs with near instant access
on slower hardware under IIS5" is incomparable. It's like saying "I had an
old diesel truck and a new lexus, and I fueled both with diesel. The lexus
choked on the diesel while the diesel truck ran great -- man, why did I ever
buy that lexus".


At this point, I have NO IDEA what your configuration looks like, how it's
been tuned, etc -- so while I commisserate with the troubles you're having,
you're really tying everyone's hands

1. Can you isolate the problem to particular pages or any random page
2. Can you isolate to certain code sequences within the pages
3. Is there a timing/sequence dependency
4. Is it just with ASP pages or with static HTML as well

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ross" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
news:6D164ECF-DF48-4290-831F-A7D9B37DA662@microsoft.com...
Like many others here, I've been tearing my hair out trying to find why IIS
6 is so slow serving ASP applications across the network. When accessing the
application from a browser on the IIS server (local access ) the pages come
up qiuckly. The same application runs with near instant access on slower
hardware under IIS 5.

I've put a workstation & the IIS server back to back with a crosover cable
to eliminate the network The performance is still poor from the workstatoin
& fast when accessed from the server. I suspect the server is trying to do
some form of authentication for non-local access, but can't seem to find
what.

I notice a lot of similar posts here, and no satisfactory answers. Its
enough to send you to Apache!!