on 06-15-2015 6:00 PM
So after reading that great article, I was eager to try this out.
I so happen to have a physical intel server 16 CPU's.
So I ran a test of a DBCHECK at parallelism 1. Took 4:20 hours.
Changed parallelism to 2, ran DBCHECK again, took 2:22 Hours.
Aprx 45% increase in time.
So Then I re-ran the same test again and the times came in within seconds of those above.
Now, I'm looking for another test, something DB extensive and that is relatively the same test each time.
I'm wondering if an SGEN would work?
Anyone have a suggestion of an SAP job I would try to benchmark and play with this?
Hi Joshua,
I don't think you can speed up SGEN because it is already run in parallel by all available application server and work process.
I also believe most standard SAP transactions can't be boosted because most ERP/OLTP queries are short and quick. If you have to test, you can find your top expensive SQL statements(custom codes) in DBACockpit -> Performance -> SQL statements. Please note that you have to drop procedure cache first in order to create a new execution plan for parallel processing.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Srikanth,
Joshua is referring to newly updated recommendations from SAP and Microsoft about settings for this parameter on modern servers with high numbers of CPU cores. The article he's referring to is http://blogs.msdn.com/b/saponsqlserver/archive/2015/04/29/max-degree-of-parallelism-maxdop.aspx. The recommendation also appears in the updated version of Note 1702408 (Configuration Parameters for SQL Server 2012).
In a nutshell, with SQL Server 2012 or 2014, if your server has 16 or more CPU cores, you can consider increasing MAXDOP to 2, or even 3 or 4 if you have 64 or more cores. For fewer than 16 cores, 1 is still the recommended setting, as it is for older releases of SQL Server.
0 is still not recommended, as that is essentially unlimited.
Dennis, that's a good suggestion for finding a good test, and also about having to reinitialize the procedure cache -- that isn't mentioned in the article that I recall, but it makes sense.
Joshua, once you've gathered some more data, you should write up a blog post with your results and observations.
Cheers,
Matt
Have you tried to set to '0' in SSMS --Advanced options?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are some BW queries that can put the MAXDOP under pressure. Unfortunately, I don't have any of them to test it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.