October 29, 2003 at 8:10 am
We are running SQL server on a quad processor machine with 3 Gb of memory. We are facing the problem that the CPU time often peaks to 100% and can even be over 80% for a longer period. After running SQL profiler we found out that the eventclass 15 (Disconnect Event) is the event that consumes the most CPU time (up to 858000 ms) and reads.
How can this happen? The SQL server is used for an IIS application.
Any help is appreciated
October 30, 2003 at 7:03 am
The duration (and i/o count) for a disconnect event is for the entire time the connection was alive. You're probably using connection pooling (the default), so the connections are for long periods; that's actually giving you better performance than if your connections needed to be rebuilt.
--Jonathan
--Jonathan
October 31, 2003 at 4:03 am
quote:
The duration (and i/o count) for a disconnect event is for the entire time the connection was alive. You're probably using connection pooling (the default), so the connections are for long periods; that's actually giving you better performance than if your connections needed to be rebuilt.--Jonathan
Thnx for you're explanation.
Wootton
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply