G
Guest
Our ASP.NET application receives around 90 anonymous hits/sec while Requests
Executing usually stays around 15-25. This is good and our server performs
well
What our app does is load a remote XML URL with xmltextreader and
xmldocument load then transcribes the XML through a stylesheet and displays
it as a webpage.
The Problem is sometimes the Requests Executing will shoot up to 125-150 and
all of a sudden we'll get a server too busy error. I don't understand why
this is happening? I tried putting this in my web.config file:
<httpRuntime executionTimeout="6"/>
But still the requests executing will jump to 125-150 and stay like that but
the anonymous rec/sec stays the same, this is driving me crazy!
Does anyone know why this is happening?
Thanks
Executing usually stays around 15-25. This is good and our server performs
well
What our app does is load a remote XML URL with xmltextreader and
xmldocument load then transcribes the XML through a stylesheet and displays
it as a webpage.
The Problem is sometimes the Requests Executing will shoot up to 125-150 and
all of a sudden we'll get a server too busy error. I don't understand why
this is happening? I tried putting this in my web.config file:
<httpRuntime executionTimeout="6"/>
But still the requests executing will jump to 125-150 and stay like that but
the anonymous rec/sec stays the same, this is driving me crazy!
Does anyone know why this is happening?
Thanks