Quantcast
Channel: ASRock Forums
Viewing all articles
Browse latest Browse all 19545

Intel Motherboards : Taichi: Turbo Boost 2.0 with E5 V3 CPU or no?

$
0
0
Author: parsec
Subject: Taichi: Turbo Boost 2.0 with E5 V3 CPU or no?
Posted: 30 Dec 2016 at 2:19pm

Originally posted by XiangS XiangS wrote:

If I use an E5 V3 CPU, does the Taichi utilize Turbo Boost 2.0? Or does the Taichi EXCLUSIVELY support 3.0, implying E5 V3 CPU's will have no Turbo Boost support. The manual isn't very clear on this, but I would assume by the manual that the Taichi does _NOT_ support Turbo Boost 2.0 for E5 V3's, as that is how it reads. The exact processor I'm using is the Intel Xeon E5-2683 V3.


"Supports Intel® Turbo Boost Max Technology 3.0
* Intel® Core
TM
i7-59xx/58xx processors only support Intel®
Turbo Boost Max Technology 2.0."


Unfortunately, the statement I underlined above contains some incorrect terminology.

Turbo Boost Max Technology 2.0 does not exist. That statement is referring to Intel's standard Turbo Boost Technology that we all know of and is a feature on many Intel processors. Just remove "Max" and the statement is correct.

That statement is not saying that Xeon E5 processors do not have Turbo Boost 2.0 Technology. It is just saying that the i7-58xx and i7-59xx models do not have the Turbo Boost Max Technology 3.0 feature.

Turbo Boost Max Technology 3.0 is a new feature that ONLY exists with four Intel HEDT processors, the Broadwell-E models, i7-68xx and i7-69xx. That means the earlier Haswell-E HEDT processors, the i7-58xx and i7-59xx models do NOT have this feature. That is all that statement is saying. 
 

This is Intel's description of TBMT 3.0:

Intel® Turbo Boost Max Technology 3.0 identifies the best performing core(s) on a processor and provides increased performance on those cores through increasing frequency as needed by taking advantage of power and thermal headroom.





Viewing all articles
Browse latest Browse all 19545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>