Is The X264 Stress Test Really Enough To Test Stability?

0
28

This is a minor update, so the results from this version can be compared with the original version 5.0 benchmark. The original idea of the old x264 benchmark was to create a stability test that would apply real world loads on a machines’ CPU for an extended period of time. This could be used to identify issues with a machine or to test whether an overclock can sustain high, real-world loads. And on the side, it provides a benchmarking result for online rankings.

If your CPU can’t keep cool at the worst of times, your cooling is not adequate. Isn’t that the fault of one’s cooling and not the software itself? I mean, it’s a benchmark, it’s SUPPOSED to 100% your CPU and temperature increase is a side effect that shouldn’t really depend on the software. Everyone at LTT uses Aida64 which is just as hot as x264 Stability Test V2, they are some of the coolest stress tests there are. Yeah, your reason for not wanting a more demanding stress test is that you want a riskier OC because you don’t think you’ll ever fully use your computer with that kind of a load. I would much rather hit a more stable, safer lower OC than take that risk.

By running a more rigorous test you reduce this possibility, the harder the stress test, the further its reduced. Video resolution can have a major impact on encoding speed and file size. The following results were produced using a Mid-2010 Mac Pro equipped with an Intel Xeon w3680 CPU with 6 cores and 12 threads running at 3.33 GHz, 24 GB memory, and macOS Mojave. A Preset is a group of settings specifically tailored for the software or device you want your videos to play on. Don’t do the opposite (don’t settle on a RF and then tweak speeds in an attempt to further tweak quality or size) as that will give highly variable results.

BurnBX loads the Northbridge, RAM, and 3.3V power supply. You’ll notice that the whole thing is pretty simplistic since I have no programming skills to speak of. Pts/scimark2 runs the ANSI C version of SciMark 2.0, which is a benchmark for scientific and numerical computing developed by programmers at the National Institute of Standards and Technology. This test is made up of Fast Foruier Transform, Jacobi Successive Over-relaxation, Monte Carlo, Sparse Matrix Multiply, and dense LU matrix factorization benchmarks.

The only way to test for all around stability is synthetic stress tests. If my overclock isn’t stable, my leisure time gets one reboot’s worth of interruption. Maybe my chart tidal health I lose a few minutes worth of work on a 3D model. I can be much less stringent with my testing methodology because the potential impact is so small for me.