OT : IIS State

Hence my reply a little up/down there about it not being the problem.
I know it's not the problem because we sucessfully ran with 10 ten times the
load but with the previous version without incident over Christmas.

What I'm trying to work out is how to to resolve it - if it can be resolved.

Tomorrows task will be code optimisation :'-(

 

The server is not failing Steve.

An application running on the server (IIS) is exhibiting undesirable
behavior due to a client of that program.

The server is happy as larry.

 

Possibly an oversimplication, but, yes. Especially in loops. Find out why
there's so much concatenation going on and do it some other way. If they're
doing something way clever like creating XML by concatenating strings
together then don't hesitate, just kill them. I had an application some time
ago that did a lot of string concatenation that would have been really
difficult to avoid. So, I wrote a small C++ COM component that implemented
an efficient 'growing' string class. It's a bit awkward in VBScript, because
you haven't got anything useful like a StringBuilder or buffers without
calling something else.

If you don't find a simple answer, get a better description of the problem
and I'll come up with something a bit more specific.

 

I are suggesting that having done some more detailed analysis of the
original evidence, I am very, very, very confident that it's an application
problem. I are also relatively qualified to be very, very, very confident.

 

You don't need to be qualified to be very, very, very confident. Of
course, being qualified/experienced it's more likely that when you're
confident you're also correct ...

 

*ding*

 

Following up on this, see if there's any huge strings involved, as the
code you originally caught this thread executing chops up allocations freed
and bungs them on the appropriate sized freelist buckets for the heap in
question.

if it then goes and makes another allocation > the bucket size for the
largest freelist, it'll take virgin heap again. This in the long run would
leave you with long unused freelists.

 

<snip>

Well the MS group were right - it did appear to be a string issue.

Changed the logic and the code today and the CPU usage went straight back
down to <30% with a responsive website.
Cheers to all for the suggestions, though I reckon that Sorby's suggestion
to change the regional settings was the thing that actually worked.

 

Jeremy thinks "taking the system down" is putting them in the lift.