Warning: Constant WP_TEMP_DIR already defined in /var/www/html/blogs/glenn/wp-config.php on line 94

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/feed-rss2-comments.php on line 8
Comments on: Recommended Intel Processors For SQL Server 2014 OLTP Workloads https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/ Semi-random musings about SQL Server performance Tue, 13 Nov 2018 18:52:27 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: useful link https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-133986 Wed, 17 Dec 2014 23:32:40 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-133986 It’s difficult to find knowledgeable people about this subject, however,
you seem like you know what you’re talking about! Thanks

]]>
By: Andrej https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6730 Mon, 12 May 2014 07:32:34 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6730 In reply to Glenn Berry.

Great, looking forward to it. If you have any considerations concerning processor selection for a SSAS-only server, I would appreciate, if you could share them

]]>
By: Glenn Berry https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6634 Thu, 08 May 2014 15:07:11 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6634 I don’t know of anyone else doing a similar analysis for TPC-H, but I might do one, especially know that we have some new results for SQL Server.

]]>
By: Andrej https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6633 Thu, 08 May 2014 14:20:15 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6633 In reply to Glenn Berry.

I meant not the benchmark itself but rather some comparison of processors similar to your blog post but with focus on DW/OLAP workloads

]]>
By: Glenn Berry https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6631 Thu, 08 May 2014 13:23:18 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6631 In reply to Andrej.

The TPC-H benchmark is for DW workloads.

]]>
By: Andrej https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6589 Wed, 07 May 2014 07:24:04 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6589 Hello Glen,

do you know whether there is a similar analysis for DWH/OLAP workloads?

]]>
By: Glenn Berry https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6268 Wed, 16 Apr 2014 15:44:16 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6268 In reply to Dillon.

Depending when they did this, it was probably not the best idea for performance and scalability. A two-socket Nehalem-EP or newer server would be much faster than an equivalent four-socket server (that was populated with only two processors).

This changes somewhat with the latest Intel E7-4800 v2 family, where the processors are much closer to the Xeon E5-2600 v2 family in performance.

]]>
By: Dillon https://www.sqlskills.com/blogs/glenn/recommended-intel-processors-for-sql-server-2014-oltp-workloads/#comment-6234 Thu, 10 Apr 2014 21:27:54 +0000 http://3.209.169.194/blogs/glenn/?p=877#comment-6234 I’ve had clients purchase servers with higher socket counts than they strictly needed, then proceed to pull out the “extra” processors, allowing them to get the specific CPUs they wanted while keeping licensing costs down.

The extra CPUs were reserved on the off chance that they’d become necessary for performance reasons, albeit with the corresponding licensing hit. I can’t remember a time that they were installed before the server itself was replaced.

That was more common back in the Xeon X7460/X7560 eras than it is now, with there now being so much diversity in Intel’s Xeon line.

]]>