Re: Any advantage to obtaining IIS6.0 for this problem?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: mko (anonymous_at_discussions.microsoft.com)
Date: 04/22/04 

Date: Thu, 22 Apr 2004 14:41:05 -0700

Firstly thanks to everyone who took the time to reply.

There is definately resource contention, the nature of the application (users are booking places/seats for a limited number of places/seats at a venue throughout the day) means that for the short time frame described the users are essentially hitting one table on the same database, requesting an exclusive at a page level lock, with each row in the table being padded out to a page size.

The data being accessed has to be locked as update operations are being performed and it's vital that 100% consistency is maintianed for read and update operations.

We are not using any application or session variables as offered by the IIS server. App Options --> enable session state is unchecked, no COM components are in the Application or Session scope that I am aware of based on my reading of the subject in Professional Active Server Pages published by Wrox.

Since changing the ASPprocessorThreadMax setting there has been no blocking with Reqests Queued staying at zero and my Requests Executing increasing over the previous limit seen of 40.

I don't think it's the network as the overall volume of traffic is low. So my hunch is database contention. As long as the users can move around the site and get their message Saving please wait when they submit a requestas opposed to a white IE screen with a blue progress bar freezing then this is a step in the right direction.