0

We have a SQL server machine - It’s a VMWare image (running on ESXi hardware etc..) It has windows 2008 x64 standard The SQL install is SQL 2008 standard The virtual machine has 12gb of RAM, and 4 virtual CPU

The box is suffering from near 100% CPU a lot of the time I enabled the AWE- but SQL server only seems to use 3-4gb of RAM

Is there a way of making it use more available ram more effectively? cache results for example..?

Improve this question
4
  • 1
    Why are you messing with AWE? you have a 64-bit system? Commented Jan 28, 2011 at 18:56
  • Are you running SQL x86 or x64? You can verify this by running SELECT @@VERSION. The output for x64 should be: Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Commented Jan 29, 2011 at 17:15
  • What are the specs on the ESXi host, and how many other VMs are running on it (how many vCPUs)? Also, what are the min and max memory settings set to on the SQL server? Commented Jan 31, 2011 at 1:16
  • Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM) Commented Feb 3, 2011 at 17:02

1 Answer 1

Reset to default
2

My limited understanding of VMware is that allocating more then one vCPU imposes a performance hit as the host needs to wait until an available slice is available on all CPU's. I could be dead wrong but as a test I would shut it down, reconfigure it with a single vCPU and see what happens.

EDIT:

In addition, indiscriminatley throwing RAM at what appears to be a CPU problem is not exactly the best approach. Some monitoring with perfmon is probably needed to track down the root cause of the CPU performance problem. It sounds like you're trying to correlate the high CPU utilization to SQL's "lack" of memory consumption, which is an erroneous conclusion to draw.

"Hmm... SQL Server is only using 4GB of RAM, that must be why the CPU is 100% utilized" is not a jump I would make without confirming it with some very in depth perfmon statistics.

Improve this answer
3
  • You're not dead wrong JoeQ but more recent releases significantly reduce this 'cpu ready' issue - of course we don't know what version the OP has so it's still valid - just wanted you to know. Commented Jan 28, 2011 at 18:55
  • Hi, thanks for your comments. The VM is hosted on vSphere4 Also, only one of the vCPU is at 100% - the others are fine... Commented Feb 1, 2011 at 16:13
  • Have you tried reconfiguring it with only 1 vCPU? I'm curious as to whether that has any bearing on the problem. Commented Feb 1, 2011 at 18:15

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.