Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

CPU considerations for multiple instances Expand / Collapse
Author
Message
Posted Friday, March 1, 2013 12:42 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 6:14 AM
Points: 65, Visits: 404
I've been researching this and haven't found much info so I'm not sure what most people do. Consider a server with 48 cores running 4 SQL instances. The server has 192GB RAM and I have max memory set per instance, but there isn't a max CPU so to speak. I have MAXDOP set to 8, but that is just per query. If multiple queries come in, one instance could spike all the cores and starve the other instances.

I'm considering enabling only certain NumaNodes for each instance. Is that the route to go?

Here's another wrench in the mix. The instances will be in a Veritas cluster so they can/will failover to another physical server. If I set specific NumaNodes for an instance, will it use the same NumaNodes on the failover server?

Any suggestions or past experiences will be appreciated!
Post #1425697
Posted Sunday, March 3, 2013 7:34 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, October 9, 2014 4:06 PM
Points: 450, Visits: 1,342
Is this OLTP or data warehousing?

For OLTP on SQL Server 2008 there's still justification for setting MAXDOP to 1. Ideally you shouldn't have any OLTP queries needing multiple cores, and if they do this option will stop them killing the server though their individual performance may suffer. With data warehousing and from SQL 2008R2 on this may not be the best option.

I don't like the idea of allocating cores to instances because if you are running Active/Active then the best use you can get from the CPUs is the sum of the allocated cores on a node, potentially half the cores which is a waste.

Using MAXDOP = 1 and monitoring CPU load would be my prefered option.

Cheers

Leo
Post #1426058
Posted Sunday, March 3, 2013 7:38 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 9:02 PM
Points: 20,734, Visits: 32,515
You should be able to assign the cores to specific instances by setting the processor affinity. Look at the properties of the instances.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1426059
Posted Monday, March 4, 2013 12:55 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:08 AM
Points: 40,207, Visits: 36,615
Typically I just let Windows balance them out via the normal scheduling. If you want to limit, rather don't use processor affinity (and please don't set maxdop to 1).

You can set CPU ratios via a windows tool. Windows resource toolkit or something like that, I forget the exact name. That lets you set limits on CPU usage for various apps



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1426106
Posted Monday, March 4, 2013 9:07 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 6:14 AM
Points: 65, Visits: 404
Thanks, I will look into that tool.

I have MAXDOP set at 8 right now. From the research I've done, that is a good setting for the amount of cores I have. Sound good?
Post #1426302
Posted Tuesday, December 10, 2013 9:47 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, September 28, 2014 1:59 PM
Points: 179, Visits: 827
You could look into utilising resource governor (built into SQL) for this very situation



SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
Post #1521581
Posted Wednesday, December 11, 2013 6:05 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, August 18, 2014 3:04 AM
Points: 1,331, Visits: 15,269
I would probably look at a combination of all of the recommendations so far.

I would set MAXDOP based on the current recommendation (No. of CPU Cores/No. of Numa = MAXDOP), not to 1 as this could limit some queries. I'd def increase cost threshold for parallelism from the default 5.

I would let windows manage the scheduling of threads itself.

I would stay away from setting the processor affinity; its something you will have to remember for server upgrades or any other changes. If you have something that is particularly heavy, I would use resource governor to manage that CPU load within SQL Server.
Post #1521857
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse