Having concluded the analysis of AMD Phenom II, we proceed to the latest platform from Intel: Core i7. We must admit that Core i7 is more interesting for a reviewer: as in case of Phenom II, we are going to "play" with the number of cores. However, while Phenom II could offer only various modes of the memory controller, Core i7 gives us two "toys": Turbo Boost and Hyper-Threading. We'll give you a recap (details on the Core i7 architecture are provided in this article devoted to the announcement of this CPU line).
This technology allows to overclock selected cores, if the current power consumption of a processor indicates that it's not working at its full capacity. Thus, Turbo Boost should theoretically have a positive effect on the speed of mostly old single-threaded software: "extra" cores may be idle in this very case. You can read about Turbo Boost in the article Intel Core i7 LGA1366 Processors.
We have known this technology since the times of Pentium 4. However, Core 2 Duo/Quad and Pentium Dual Core "forgot" about it, and now Core i7 brings it back to life. Hyper-Threading (HT) allows to emulate two logical cores (detected by an operating system) based on a single physical core by sending commands from two parallel threads to one physical core. The main idea behind it is that some execution units in a core are almost always idle, because there are no "proper" commands for them. But if we execute two threads on a single core, all execution units may be loaded, which will increase the overall efficiency of the system. But there is one tiny "but": Intel had to make some sacrifices to implement this theoretically perfect idea -- not all units can be shared between two virtual cores dynamically. In particular, load/store/reorder buffers are just shared between two virtual cores in half, when HT is enabled. Thus, even if one of virtual cores is idle, technical characteristics of the other virtual core are worse than those of a single physical core, when HT is disabled. And its performance in some cases may be lower for absolutely objective reasons. Intel optimistically has it that there are few such cases. Well, we have a great opportunity to see whether it's actually true.
We should remind our readers of similar tests conducted over Intel Core i7 920 using our previous version of test procedure (2008). We'll tell you right away: our decision to run the tests one more time using the updated test procedure was absolutely correct. We got different results.
- CPU: Intel Core i7 950
- Cooler: ASUS Triton 81
- Motherboard: ASUS P6T SE (Intel X58)
- Memory: 3 x 2GB Corsair DDR3-1800 in DDR3-1600 mode
- Graphics card: Palit GeForce GTX 275
- PSU: Cooler Master Real Power M1000
All tests were run on the same testbed, only BIOS options were subject to changes: we disabled both Turbo Boost and Hyper-Threading at first, then we enabled Turbo Boost, then we disabled Turbo Boost and enabled Hyper-Threading, and finally, we enabled both technologies. Like in the previous parts, in this article we use diagrams with an average score for each group and tables with results obtained in each application. This craving for details is quite explainable: we examine technologies, which may affect the speed of real programs in different ways, and this series of articles was intended to find out these details.
Besides, we traditionally publish a link to a Microsoft Excel spreadsheet for curious readers, which contains all test results in the most detailed form. Besides, it includes an additional tab "Compare" to facilitate their analysis. Just like the tables in the article, it compares the four situations percentagewise. The tables compare all systems with the same configuration -- with Turbo Boost and Hyper-Threading disabled (leftmost column). Tables are colored in the traditional way: bright blue background marks outstanding positive results (in this case we marked performance gains above 10%), red background signals problems: performance drops where we should have performance gains (or at least no changes).
||TB & HT disabled
||TB & HT enabled
|3ds max ↑*
|UGS NX ↑
|Group Score ↑
* -- The up arrow (↑) marks tests, where the highest results are the best, the down arrow (↓) marks tests, where the best results are the lowest.
Visualization does not respond much even to physical cores, so results of enabled HT are encouraging: at least something. However, we are disappointed by SolidWorks results: having gained 15% from TB, it responded negatively to enabled HT. As a result, this program gets a lower performance gain that it's due in the nominal mode (both TB and HT are enabled): it would have been 15% without HT, and now it's only 9%. 3ds max demonstrates a perfect partnership of technologies: +9% from TB and +7% from HT total +17% to the speed (rounding up added another +1). On the whole, 3D visualization programs feature weak optimizations for multithreading, so they gain more from Turbo Boost. It agrees with our initial assumptions.
||TB & HT disabled
||TB & HT enabled
|3ds max ↑
|Group Score ↑
Such a perfectly parallel process as rendering expectedly welcomes Hyper-Threading. On the other hand, that's exactly what explains mediocre results from Turbo Boost: when all four cores are loaded, heat release it close to maximum, and it makes no sense to increase the frequency. Lightwave is a champion in squeezing everything from a processor. We don't know whether this article will be read by programmers working on this package, but we'd like to thank them: this program is optimized perfectly.
Write a comment below. No registration needed!