Post reply

CPUTime vs DiskIO time

  • April 2, 2010 at 7:46 am

    #220028

    My company SQL Server 2005 db would grind to a halt daily. I suspect some apps are opening connections and not properly closing it. There are many web apps and I'm in the process of investigating all of them.

    In addition, I was reading the following article which mentions if CPUTime is high and DiskIO is low, it indicates a bad execution plan and can cause problems.

    http://sqlserverplanet.com/sql-server-2008/sql-server-slow-performance/[/url]

    so I executed the Sp_who2 stored procedure and noticed the following.

    one process (Visual Importer Enterprise) had:

    CPUTime: 14054

    DiskIO: 102

    Is that bad?

    thanks,

    Psion

  • April 2, 2010 at 8:08 am

    #1144763

    There a number of things that can cause a server to "grind to a halt" as you say. sp_who2 is a good tool to help identify the causes. Typically blocking or insufficient memory are prime culprits but there are others.

    You need to look at system performance monitor as well as process activity in SQL server to get a picture of what is going on and which resources are being used and which might be in contention.

    The probability of survival is inversely proportional to the angle of arrival.

  • April 2, 2010 at 8:14 am

    #1144770

    Thanks for the reply. I'm in the process of doing that now. It was difficult finding out what all the indicators in perfmon means but I found this website (in case someone else was looking)

    http://dotnetdebug.net/2005/06/30/perfmon-your-debugging-buddy/[/url]

    -Psion

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply