How CPU Features Affect CPU Performance, Part 3
|
Scientific and engineering analysis
|
TB & HT disabled |
TB enabled |
HT enabled |
TB & HT enabled |
Maya ↑ |
9.49 |
10.17 |
7% |
9.82 |
3% |
10.24 |
8% |
SolidWorks ↓ |
38.55 |
35.56 |
8% |
40.96 |
-6% |
35.78 |
8% |
Pro/ENGINEER ↓ |
1554 |
1445 |
8% |
1539 |
1% |
1491 |
4% |
UGS NX ↑ |
5.41 |
5.78 |
7% |
5.57 |
3% |
5.72 |
6% |
MAPLE ↑ |
0.2197 |
0.2279 |
4% |
0.2197 |
0% |
0.2227 |
1% |
Mathematica ↑ |
3.2357 |
3.371 |
4% |
3.0364 |
-6% |
3.1403 |
-3% |
MATLAB ↓ |
0.038867 |
0.036974 |
5% |
0.040566 |
-4% |
0.03898 |
0% |
Group Score ↑ |
139 |
148 |
6% |
137 |
-1% |
144 |
4% |
No "blue flags", only four red ones, three of which refer to Hyper-Threading. Turbo Boost desperately pulls the total score up, but it sometimes fails to cope with heavy performance drops caused by HT: pay attention to results in Mathematica. Engineering packages perform very strangely: +8% from TB and -6% from HT in SolidWorks transform into the same +8% from both technologies enabled. It looks as if Hyper-Threading does not affect performance in this application without Turbo Boost. But the bad influence disappears as soon as TB is enabled. Pro/ENGINEER also behaves in a strange way: performance gain from TB equals 8%, from HT -- 1%, and the total performance gain... is just 4%.
Raster graphics
|
TB & HT disabled |
TB enabled |
HT enabled |
TB & HT enabled |
ACDSee ↓ |
05:04 |
05:08 |
-1% |
05:21 |
-5% |
04:45 |
7% |
Paint.NET ↓ |
00:18 |
00:17 |
6% |
00:15 |
20% |
00:14 |
29% |
PaintShop Pro ↓ |
09:20 |
08:41 |
7% |
09:48 |
-5% |
08:46 |
6% |
PhotoImpact ↓ |
06:20 |
06:04 |
4% |
06:33 |
-3% |
06:10 |
3% |
Photoshop ↓ |
05:46 |
05:05 |
13% |
05:50 |
-1% |
04:53 |
18% |
Group Score ↑ |
138 |
146 |
6% |
138 |
0% |
154 |
12% |
Microsoft.NET platform (represented by Paint.NET) proves its positive attitude to various "boost" technologies again. However, the overall situation in the bitmap graphics group is not very peachy: ACDSee acts very strangely, PaitShop Pro, PhotoImpact and Photoshop respond negatively to HT. Only Photoshop manages to use TB properly, even though it also has good multithreading optimizations. These results also lack logic and common sense: two minuses in ACDSee add up to a plus. Photoshop also shows funny arithmetics: 13 minus 1 equals 18 there.
Data compression
|
TB & HT disabled |
TB enabled |
HT enabled |
TB & HT enabled |
7-Zip ↓ |
03:45 |
03:37 |
4% |
03:46 |
0% |
03:37 |
4% |
WinRAR ↓ |
01:19 |
01:09 |
14% |
01:15 |
5% |
01:07 |
18% |
Group Score ↑ |
138 |
151 |
9% |
142 |
3% |
153 |
11% |
It's a logical situation: no archiver can use more than two threads to pack files into its own format, so Turbo Boost is much more useful here than Hyper-Threading. But the latter gives a surprise again: WinRAR inexplicably benefits from enabled HT -- but we know for sure that this archiver cannot use even four cores, to say nothing of eight.
You might have already noticed that our study of how HT and TB interact with real software resembles riding a jibbing horse: nobody knows what's inside its head and where it will bolt the next moment. So the only thing you can sometimes do is to relax and enjoy the view, trying to remain in the saddle.
Compiling
The new compile test handles four physical cores well, and it did well with eight virtual ones: Hyper-Threading yields 23% of performance gain.
Audio encoding
Audio codecs running in parallel (as many as cores) should have been the ideal environment to reveal all positive traits of Hyper-Threading: as we have already determined from indirect signs, their computing core is most likely stored in cache, and their algorithms should agree with the HT concept well. Test results confirm our assumptions: performance gain from HT amounts to 28%. Turbo Boost yields smaller dividends, but they are still good. But the most successful results are demonstrated, when these technologies work together: 45% performance gain! That's the highest result in our tests here, by the way.
Write a comment below. No registration needed!
|
|
|
|
|