Server Consolidation

  • Hello All, Our entire domain is on VM.The CPU's usage rarely goes above 20%.Is it advisable to consolidate from a CPU perspective?Can we reduce the CPU count ?

    This is what has been used to capture CPU Usage. Please advise.

    cpu_idle = record.value('(./Record/SchedulerMonitorEvent/SystemHealth/SystemIdle)[1]', 'int'),
    cpu_sql = record.value('(./Record/SchedulerMonitorEvent/SystemHealth/ProcessUtilization)[1]', 'int')
    FROM (
    SELECT TOP 1 CONVERT(XML, record) AS record
    FROM sys.dm_os_ring_buffers
    AND record LIKE '% %'
    ) as cpu_usage

    • This topic was modified 6 months, 3 weeks ago by  mtz676.
  • Remember, that's a VM, so you're reading what it thinks it sees from within that VM. You should also run queries against the hypervisor to see how much CPU is being consumed there.

    Also, I'd never rely on a single measure to make these kinds of decisions. What do your wait statistics look like? What are the principal causes of waits & queues on the system? How many waits or cues are CPU related? Do you have aggregate measures of CPU use for your queries? What about the worst performing queries? How is their CPU use? And waits?

    Gather all this data, not just the one data point. Then, the decision will be silly simple.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • @Grant Fritchey. Thanks for the response. Will do so.

    • This reply was modified 6 months, 3 weeks ago by  mtz676.
    • This reply was modified 6 months, 3 weeks ago by  mtz676.
    • This reply was modified 6 months, 3 weeks ago by  mtz676.

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

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