Intel Core i9-10900K in the versatility test. What are the strengths and weaknesses of the last 14-nm bolide?

1 - Introduction and test setup 2 - Graphic benchmarks: Gaming 3 - Graphic benchmarks: Workstation Real-Time 3D 4 - Graphic benchmarks: Workstation Composite 5 - CPU benchmarks: Composite und I/O 6 - CPU benchmarks: Rendering 7 - CPU benchmarks: Compute and HPC 8 - Power Consumption 9 - Summary and Conclusion

Now we have finally arrived at the creation area and want to dedicate ourselves to rendering. From now on, by the way, the up to now astonishingly frugal Intel Core i9-10900K will also become a drinking buddy, but more about that later. Now it’s time to really sweat! And the first benchmark shows why sometimes even the cores are pretty much everything, because the old enthusiast platform from Intel comes to life again. Well, it’s not enough for the head of the Ryzen Family, but the 12-core has to be springy.

Interesting is 3ds MAX, because here the Core i9-10900K performs amazingly well. Of course, you can see that from the power outlet and the temperatures, but where there’s a will, there’s also a chiller. With air, it would probably go out pretty quickly.

When I throw my mascot into the ring, it almost looks like Solidworks again. The country needs more cores! But not always.

In the flying classroom, the older Core i9-9980 XE then takes off completely, but also at the power outlet. And you can see very clearly what only two cores more make up when you compare the Core i9-10900K with its i9-9900K(s) siblings.

Once again Blender, but now for the penultimate time. The Core i9-10900K is passed through one more place, the rest remains as before.

The last Blender run is more a combination of raytracing and kerfuffle, so it’s no longer a pure parallel world. And Schwupps, the Core i9-10900K is back on top again, while the two 9900 brothers take a slight timeout.

In the Luxrender, Intel’s 2066-Garde suddenly dominates and even beats both Ryzen 9’s. This makes the difference between the WPC command line renderer and the standalone benchmark. A prankster who immediately thinks of the compiler. But even that is (still) there and just had to be shown.