Why is SQL Server setup recommending MAXDOP 8 here?
16
votes
2
answers
3358
views
I'm running SQL Server 2022 RC1 setup on an AWS i3.16xlarge with 2 sockets, 2 NUMA nodes, 32 logical processors per node, 64 logical processors altogether.
Setup is recommending MAXDOP 8:
But if you click on that link for configuring MAXDOP , the recommendations say:
Based on that KB article, MAXDOP should be 16, not 8. Sure, technically 8 is less than 16 - but so is 2, or 4, or 15. Where's the 8 coming from?
After SQL Server installation finishes and the service starts up, the log shows that SQL Server is automatically implementing Soft-NUMA with 4 nodes, each with 16 logical processors:
So again, that indicates that MAXDOP should be 16.
Is this a bug, or did I miss something obvious? Is there another unwritten rule somewhere that setup will stop at MAXDOP 8?
But if you click on that link for configuring MAXDOP , the recommendations say:
Based on that KB article, MAXDOP should be 16, not 8. Sure, technically 8 is less than 16 - but so is 2, or 4, or 15. Where's the 8 coming from?
After SQL Server installation finishes and the service starts up, the log shows that SQL Server is automatically implementing Soft-NUMA with 4 nodes, each with 16 logical processors:
So again, that indicates that MAXDOP should be 16.
Is this a bug, or did I miss something obvious? Is there another unwritten rule somewhere that setup will stop at MAXDOP 8?
Asked by Brent Ozar
(43335 rep)
Nov 3, 2022, 04:38 PM
Last activity: Nov 3, 2022, 10:01 PM
Last activity: Nov 3, 2022, 10:01 PM