Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

Write for Us

Share you SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Policy Based Management in SQL Server 2008
Inside SQL Server Cluster Setup and Troubleshooting Techniques - Part I ...
Configure and Manage Policy Based Management in SQL Server 2008 ...
Using Column Sets with Sparse Columns

More     
 
Latest FAQ's

Cannot Start SQL Server Service
Users are able to connect to report manager but not able ...
Errors when SQL Server Snapshot Replication is Running
How to Display Server Name or IP Address in a Reporting ...

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

Are more CPUs better than fewer CPUs for the best performance from SQL Server?



Question

All other things being equal, which of the following CPU options is the better choice for heavy-duty queries in SQL Server 2000:

--A single Xeon CPU running at 2.4 GHz (with 512KB L2 cache)
--Quad Xeon running at 550 MHz (with 1MB L2 cache)

Also assume that the server would have 1GB of RAM.

Answer

Assuming that your server is running heavy-duty queries that can take advantage of SQL Server's ability to use query parallelism, I would go for the quad Xeon. Multiple processors allow your queries (and some other SQL Server tasks) to run in parallel, and the larger L2 cache in the quad Xeon CPU example you gave also offers performance gains.

But the answer to your question may not be this clear cut. If your server is very heavily loaded, running heavy-duty queries most of the time, then the quad Xeon is the better choice. But if your server is not very heavily loaded, or if not too many of the queries can run parallel, then the faster, single CPU, may actually be faster.

If you are confident that your assumptions are correct, let that be your guide. But if you aren't confident in your assumptions, then you may (if possible) try to run some tests to see how your particular application fares under both configurations.

From another perspective, keep in mind that the most common bottlenecks that SQL Server runs into are memory and I/O, not CPU. For example, if cost is a big issue, you might want to get the single, fast Xeon CPU with 4 GB of RAM instead of a quad Xeon server with only 1 GB of RAM. Or, you might consider getting a server with room for quad CPUs, but only add one or two now, and only add the others if you find that your server has a CPU bottleneck.

Also, you may want to consider the Intel's Duo Core CPUs. They give you the full benefit of two CPUs for only one slot and a single SQL Server CPU licensing fee.








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved