Results: Media And Encoding
This OpenCL-based rendering test shows the Z1 with a roughly 10 percent lead in both tests. The margin is tighter than what we saw from the V-Ray RT test, but HP still has an edge.
Cinebench shows the Z1 in front by 8.4 percent running on one core; it leads by two percent in the threaded version of the test. Why the difference between quad-core processors? More than likely, greater memory bandwidth helps propel performance a bit compared to the Xeon.
In the Cinebench OpenGL test, the Z1's faster GPU pulls away from the baseline machine, speeding off to a score that's 1.7 times faster.
The very long chart below includes all of the viewperf results. Similar to the OpenGL- and DirectX-based real-world preview tests, we ran viewperf on the Z1 at 1920x1080 and its native 2560x1440.
Even at its native resolution, the Z1 outperforms our baseline system. And as we've seen before, certain tests perform slightly better with AA on.
Euler3D's wing simulation, being entirely CPU-bound and with a rather small memory footprint, gives us predictable results due to the Z1's slightly faster processor and greater memory bandwidth.
The Z1's slight improvement in our TotalCode benchmark (less than three percent) is in-line with other benchmarks where CPU speed is the deciding factor.
The HandBrake results are inconsistent with our other tests. Despite multiple runs to check the results, the Z1 loses to the baseline system by a hair.
The same thing happens in LAME, which is single-threaded and should favor the Z1's 100 MHz-higher peak Turbo Boost frequency. Our baseline system still ends up on top though, and the only thing we can think of is lower memory latencies that might help compensate for the clock rate difference.
In our Chrome compile test, the Z1 enjoys a nice lead. Our best guess to explain the difference is the Z1's two-drive RAID configuration preventing a storage bottleneck. The HP workstation's additional memory capacity and bandwidth might also come into play.