(TL DR: Blender 3.x is faster than all others. GPU testing started with Blender 2.80, as older Blender versions are not compatible with our GPUs anymore. The same CPU and GPU machines were used for each individual test. Here’s how we set up this test: each frame (or frame group) was rendered twice, and the shortest time was considered.

So please look at the samples/resolution settings for each file, to put the results in the correct context. We did alter the resolution and samples count for some of the files, to make the differences more visible. To that, we added one Eevee file, as Eevee projects are also rendered on our farm. We used the Blender splash screen images for this purpose, as they offer enough variety and they are more complex than the ‘original’ benchmark suite. This sparked a new question – are there speed differences between various Blender versions, too? And this is a question we can answer, seeing that at the time of writing this, we support Blender starting with version 2.75 until version 3.4. And a small fraction of the projects actually render faster on CPU – usually, projects that make use of volumetrics and/or motion blur may fall into this category. Some projects render way faster on the GPU servers. Some projects render in comparable times on our CPU and GPU machines. Starting with Blender 3.0 we have noticed that, for the exact same hardware, different projects behave in quite different ways. The resulting data sometimes shows interesting side results in this case, I’m going to refer to speed differences in rendering. During this time, we monitor all the processes, to be able to proactively make adjustments and fixes, when necessary. _WidgetManager._RegisterWidget('_ImageView', new _WidgetInfo('Image10', 'upload-image', document.We render tens of thousands of frames every day, 365 days per year.

Window = 'AOuZoY7xyMDAXILPwVTO8UVjrBfYBeeoFQ:1681407290911' _WidgetManager._Init('//_WidgetManager._SetDataContext()

Blender current version