Today we’re sharing some initial performance results, and publishing the code to collaborate with Cycles contributors. There’s just enough functionality to render some of our benchmark scenes now. To that end, we’ve implemented a prototype of a new GPU kernel, and new scheduling algorithms for viewport and batch renders. Our first target was to validate the new architecture. Introduce more advanced rendering algorithms.Improve performance on modern CPUs and GPUs.Improve usability of viewport and batch rendering.Improve the architecture for future development.The Projectīroadly speaking, the goal of the project is to: Rather than finding quick fixes or optimizations that solve only part of the problem, we’re rethinking the architecture as a whole. To address that, Sergey and I started a research project named Cycles X, with the aim is to refresh the architecture and prepare it for the next 10 years.

However some decisions made in the past are holding back performance and making it difficult to maintain the code. We’re keen to make bigger improvements to core Cycles rendering. We learned a lot in those 10 years, things that worked well, but also things that didn’t work well, or became outdated as rendering algorithms and hardware evolved. In the past decade Cycles has developed into a full-fledged production renderer, used by many artists and studios.

Today it’s been exactly 10 years since Cycles was announced.

Multiple versions of blender on mac