Home » Blender » Cycles versions speed comparison. CPU and GPU

Cycles versions speed comparison. CPU and GPU

Last updated on by .

Blender’s fast-paced release cycle is a unique differentiator in the 3D modeling world. Its purpose is to come up with new features, updates and bug fixes fast. Among the trade-offs stands a continuous learning process and the fact that there are bugs that need to be fixed. But this is part of Blender’s charm, and I think it’s well worth it.

During the last few releases, the ‘Cycles improvements’ section in the release notes has been constantly populated. And almost all recent releases come with the promise of speed improvement.

At RenderStreet, we probably have the widest array of Blender versions available for rendering from all render farms (2.63 and upwards). So we put on our scientist lab coats in an attempt to test them out, see how they perform on server-grade hardware and identify the best version available for our users. The model of choice was the Pabellon Barcelona Cycles scene that Hamza Cheggour published on his eMirage site. This file is on its way to replace the famous BMW as the ‘standard’ benchmark for Cycles, so we decided to use it for this purpose.

The tests started with a̶ ̶b̶e̶e̶r̶  Blender 2.66 and went through the newest version, Blender 2.71. Server configurations used were 2 x Tesla M2090 for GPU, and 2 x Xeon E5-2670 for CPU. RenderStreet render times for Blender Cycles are revealed in the chart below:

Looking at the results, we were blown away by the figures and what the developers did over the recent years. Speed in Blender 2.71 is almost twice as fast as it was in 2.66. With the exception of 2.67 when GPU rendering had a glitch, the numbers have been improving continuously. Also, the latest Blender release unleashes the potential of our Dual-Xeon servers. The CPU render times are getting very close to the GPU times (2 seconds). This means that complex – texture and geometry – heavy scenes that require CPU can be rendered just as fast with RenderStreet.

Cycles test conclusions

If possible, you should always use the latest version of Blender. It will give you the best performance, not to mention all the new features that get implemented. When used on a render farm, this will have a direct impact on your costs. Of course, I advise you to test each project with the new version first, and run it through your Mark One Eyeball validator, to make sure the result is the desired one.

Go Cycles, go Blender!

Update October 2014: 

Blender 2.72a was released, and we added it to our test. This version is the first one to make the switch to CUDA 6.x (we are using 6.5 in this test), and this brings slightly slower renders on GPU. At the same time, the CPU rendering is even faster, which has as a result our CPU servers outperforming the GPU ones.


Passionate about technology and constantly working on making a difference, Marius is RenderStreet’s CEO.

  • Nkansah Rexford

    Interesting stuff. Blender is getting better by the release.

  • Igor Vrana Korček

    What settings have been used for this scene? I would like to compare to my computing power.

    • Igor, since this article has been published, the environment has changed: we added a different kind of GPU servers to our farm, which are two times faster than the old ones. Also, Blender is now at version 2.76b, and all that will make the results difficult to compare. If you want to test our service, I suggest you to create an account, and use the signup bonus to render a few of your scenes with the current Blender version