Parallelism defaults that surprise production
Cost threshold for parallelism and MAXDOP left at defaults can cause CX waits, worker starvation, or underused CPUs.
Parallel plans are not free. Defaults that made sense in another era still sit on modern servers and show up as wait-stat noise or CPU storms.
What we evaluate
- MAXDOP relative to cores, NUMA, and workload mix
- Cost threshold for parallelism still at the historic default on systems crushed by tiny parallel plans
- Concurrent heavy queries stacking workers
- Reporting and OLTP sharing an instance without workload governance
There is no universal “set MAXDOP to X”
Vendor folklore spreads faster than measurement. The right answer depends on:
- Hardware topology
- Concurrent user load
- Query mix (OLTP vs warehouse)
- Whether a few monsters dominate CPU
Health check vs tuning engagement
A health check flags suspicious defaults and related wait patterns. Deep tuning validates changes with before/after metrics on your critical queries — not a blog post’s favourite number.
Need hands-on SQL Server help?
Allay Data Solutions offers maintenance, tuning, and assessments from Port Elizabeth, South Africa.