CPU Pegging

I have
Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
I am noticing the processors are pegging quite a bit, cpu for the
sqlservr.exe process is running around 50% constantly with lots of pegs up
to 100%. Is there something I should be looking at before I throw more
hardware at it? Is this normal, knew sql server sucked memory but not the
cpu. The memory for the process is around 1.6 gig. It is a production
machine so it is hit pretty hard during the day.
John"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> I have
> Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> I am noticing the processors are pegging quite a bit, cpu for the
> sqlservr.exe process is running around 50% constantly with lots of pegs up
> to 100%. Is there something I should be looking at before I throw more
> hardware at it? Is this normal, knew sql server sucked memory but not the
> cpu. The memory for the process is around 1.6 gig. It is a production
> machine so it is hit pretty hard during the day.
> John
>|||Well, you might want to look at profiler and see if there are specific
queries that can be better tuned or rewritten
"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:u4sV1n1vDHA.1424@.tk2msftngp13.phx.gbl...
> "John Cantley" <jcstrider@.hotmail.com> wrote in message
> news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> > I have
> >
> > Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> >
> > I am noticing the processors are pegging quite a bit, cpu for the
> > sqlservr.exe process is running around 50% constantly with lots of pegs
up
> > to 100%. Is there something I should be looking at before I throw more
> > hardware at it? Is this normal, knew sql server sucked memory but not
the
> > cpu. The memory for the process is around 1.6 gig. It is a production
> > machine so it is hit pretty hard during the day.
> >
> > John
> >
> >
>|||Oh, and as an aside, if your pegging CPU, one thing to look for is cursors.
"John Cantley" <jcstrider@.hotmail.com> wrote in message
news:u4sV1n1vDHA.1424@.tk2msftngp13.phx.gbl...
> "John Cantley" <jcstrider@.hotmail.com> wrote in message
> news:uc2glj1vDHA.2304@.TK2MSFTNGP12.phx.gbl...
> > I have
> >
> > Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> >
> > I am noticing the processors are pegging quite a bit, cpu for the
> > sqlservr.exe process is running around 50% constantly with lots of pegs
up
> > to 100%. Is there something I should be looking at before I throw more
> > hardware at it? Is this normal, knew sql server sucked memory but not
the
> > cpu. The memory for the process is around 1.6 gig. It is a production
> > machine so it is hit pretty hard during the day.
> >
> > John
> >
> >
>|||| I have
|
| Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
|
| I am noticing the processors are pegging quite a bit, cpu for the
| sqlservr.exe process is running around 50% constantly with lots of pegs up
| to 100%. Is there something I should be looking at before I throw more
| hardware at it? Is this normal, knew sql server sucked memory but not the
| cpu. The memory for the process is around 1.6 gig. It is a production
| machine so it is hit pretty hard during the day.
--
Hi John,
The most important question you need to ask yourself as a DBA: are your
users complaining about slowness or lack of responsiveness? If not, then
things are fine. The old adage goes, "if it ain't broke, don't fix it."
High CPU utilisation, as long as it's not always running at 100%, is
actually a GOOD THING. That means that the CPU, the most expensive
component of a computer system, is doing it's job. If you see CPU spiking
to 100% on occasion, that means there are no bottlenecks in your computer
system.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||Eric,
Ok just wondering then.
I have a smaller server that runs our website content and customer order
data, I coded the application and made heavy use of stored procedures,
triggers and such. The cpu is typically under 10% and mem usage is about 1/2
gig and connections are usually in the 50 range. The site is heavily used
for order tracking and other stuff.
The one that is causing me problems is a bigger faster machine with two
processors, I have no control of the frontend application that is used in
our production process, it uses 0 stored procedures, 0 triggers, nothing
nada zilch. I am thinking that since this is true then I am not getting a
good rate of the sql statements compiled, since so many varying queries are
hitting it. I have also noticed 3 connections opening just upon startup of
the application. Couldn't these factors account for the higher cpu usage. I
preformed a backup on it and noticed that the cpu usage dropped to a lower
rate. I am thinking that maybe the transactions are left dangling by the 3rd
party product and the backup process terminates them.
john
"Eric Cardenas" <ecard@.anonymous.com> wrote in message
news:pfOA846vDHA.3532@.cpmsftngxa07.phx.gbl...
> | I have
> |
> | Dell 6450 with 2 Pentium 3 Xeon 700mhz processors and 2 gig of ram
> |
> | I am noticing the processors are pegging quite a bit, cpu for the
> | sqlservr.exe process is running around 50% constantly with lots of pegs
up
> | to 100%. Is there something I should be looking at before I throw more
> | hardware at it? Is this normal, knew sql server sucked memory but not
the
> | cpu. The memory for the process is around 1.6 gig. It is a production
> | machine so it is hit pretty hard during the day.
> --
> Hi John,
> The most important question you need to ask yourself as a DBA: are your
> users complaining about slowness or lack of responsiveness? If not, then
> things are fine. The old adage goes, "if it ain't broke, don't fix it."
> High CPU utilisation, as long as it's not always running at 100%, is
> actually a GOOD THING. That means that the CPU, the most expensive
> component of a computer system, is doing it's job. If you see CPU spiking
> to 100% on occasion, that means there are no bottlenecks in your computer
> system.
> Hope this helps,
> --
> Eric Cárdenas
> SQL Server support
>