"Egbert Nierop (MVP for IIS)" <egbert_nierop.RemoveThis@nospam.invalid> wrote in
message news:OG9WKDiGEHA.2768@tk2msftngp13.phx.gbl...
> This would happen *only* if you store VB6 com objects in the session or in
> the application.
> Also, it is possible that your SQL statements are badly optimized
(regarding
> indexes and so)...
We are running a web class application - this week we changed the front end
to use ASP that talks to the web classes in step 4 of a process, where
previously web classes managed it all.
Prior to the change, the websites handled literally ten times the load
without problem - as soon as we changed to the ASP based solution I'm seeing
this behaviour.
A Webclass reference is created in the Application_OnStart, however it was
created before as well. Previous misbehaviour was the occasional crashing of
the IIS process, but never locking like this.
The SQL is something I'm looking at, however overall the columns are indexed
correctly and performance wise SQL seems fine - it's certainly not working
very hard when I monitor the SQL server.
That said, I had to increase the max. connection limit on teh SQL server as
soon as we changed to the ASP app - previously the web classes never created
as
many connections.
> > 3) immediate jump to 60%+ with an iisstate result like I originally
> posted -
> > slow response - request queue grows like mad in perf. mon.
>
> Typically happens with thread affinity loving COM objects...
Which is a possibility, though in this case we now use the COM objects LESS
then we did before.<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIS State - help appreciated