Blender 2.75 opencl benchmark full#
Blender 2.75 opencl benchmark software#
Blender 2.75 opencl benchmark free#

Yet in the current chosen camera angle the desk items account for less than 5% of the shot.

Blender 2.75 opencl benchmark full#

Not to criticize the scene but just as an example, the classroom in these benchmarks has so much detail on the desk you could do a full HD close up render of it. Add to the fact that Blender now pretty much allows keyframing any setting means that subsurf levels can be animated according to the distance of the objects, or decimate modifiers etc. I have however built many scenes with a fair level of complexity and they rendered just fine on my old Gtx 570, and that was a 1gb card. Same, or slightly longer with the exception of ‘koro’ where the gains made by setting the tile size to 160*120 seemed to disappear. Render time using the “magic” tile size of 160*120.įrom the March 23 to Apbuild, the render times were about the _3_1:13:04.44_43:19.95įor most (but not all) files, there was a fairly substantial reduction in RAM: DDR4 2667 MHz – 64GB Total (16GB x 4)Ĭorrected crashes due to using a single graphics card, both for renderingĪnd display, by increasing the TDR timeout value as described at:īlender version used: 2.77 Build date: March 23,2016

Blender 2.75 opencl benchmark free#

But… who knows what the future brings.įeel free to post own stats and observations on this blogpost! Maybe other .blend files should be added?ĬPU: Intel Xeon W-2145 8 Cores, 16 Threads 3.7GHz That confirms our own experience that fast GPU is great for previewing and lighting work, and fast CPU is great for the production rendering. When shots get more complex, CPUs win the performance battle. Most strikingly so-far is that the performance of CPUs is in a similar range as GPUs, especially when compared to costs of hardware.

We aim at updating it regularly, also when new hardware comes in – and especially when render features improve in Cycles.

The goal is to have an overview of systems that are used or tested by developers of Cycles. On the links below you can inspect the spreadsheet with results, and load the. We take a privacy-conscious approach when handling Benchmark data.Blender Institute prepared six Blender files for testing Cycles rendering with CPU/GPU, using various settings and design styles but based on actual production setups. Permanent - Data should be made available at a stable Internet location indefinitely and in a stable data format for as long as possible.Online and Free - Information is not meaningfully public if it is not available on the Internet at no charge, or at least no more than the marginal cost of reproduction.Reasonable privacy, security and privilege restrictions may be allowed. License-free - Data is not subject to any copyright, patent, trademark or trade secret regulation.Non-proprietary - Data is available in a format over which no entity has exclusive control.Non-discriminatory - Data is available to anyone, with no requirement of registration.Machine processable - Data is reasonably structured to allow automated processing.Accessible - Data is available to the widest range of users for the widest range of purposes.Timely - Data is made available as quickly as necessary to preserve the value of the data.Primary - Data is as collected at the source, with the highest possible level of granularity, not in aggregate or modified forms.

Public data is data that is not subject to valid privacy, security or privilege limitations.

Complete - All public data is made available.We believe that Blender Open Data should be:

Blender 2.75 opencl benchmark software#

We aim to compare performance variation in software and hardware to support the BlenderĪs initial guideline for our definition of Blender Open Data, we were inspired by Blender Open Data is a platform to collect, display and query the results of hardwareĪnd software performance tests - provided by the Blender community.