CMZTECH.NET
  • Blog
  • Graphics
  • Virtual Reality
  • 3D Printing
  • Fun Stuff
  • Contact

Blender 2.81 and OPTIX

11/22/2019

0 Comments

 
This is a pretty exciting week for Blender users with 2.81 dropping.  As well as a host of new features it offers improved performance when rendering.  I decided to take a look, since performance influences which renderer to use.  In my case, I love the look of cycles but I'm just too impatient.
Using a scene from a project I just finished I decided to compare 2.8 with 2.81 as well as with the latest Studio Ready driver from NVIDIA.

Summary: 
For my limited test scene on my specific computer: 
  • 2.81 halved my render time using Eevee.  >54% gain.
  • 2.81 cycles with OptiX decreased my render time by a quarter. >25% gain.
Win!

Note: I didn't compare the output images except visually. They look about right, I don't know how different the pixels are, it isn't something I'm that concerned about.  If you need to match footage between versions that might be something you care about. 

Your mileage is going to vary! My scene probably has all kinds of weird stuff in it and for my cycles renders, there is still a lot of noise.  That's partly because I did the project using Eevee so I didn't care about the lighting for Cycles.  The Eevee and Cycles renders look totally different.
My system is an off the shelf HP Omen desktop running Win10 .
  • i7 9700F
  • 16GB
  • RTX 2060
Eevee Performance
Switching from 2.8 to 2.81 gained me a significant performance increase. 
This increase did not change with the new OptiX driver. 

Blender Eevee Time to Render Per Frame for 24 Frames
  • 2.8   = 2.6 Seconds
  • 2.81 = 1.2 Seconds

Pretty nice lift right?  Basically my Eevee renders now take less than half the time.

Cycles Performance
Blender Cycles Time to Render a Single Frame
  • 2.8 = 90 Seconds
  • 2.81 =  262 Seconds  <-- this is bad and wrong and I'm a doofuss.
Wait? What? Dur.  Important point here.  You need to go into:
Edit->Preferences-> Cycles Render Devices
and set your preferred rendering system. If you have it set to none which is the default, its going to render on the CPU which will be slow.  
Picture
Set your preferences!
Cycles Performance Take 2
By the time I realized the mistake above I'd already installed the latest Studio Ready driver from NVIDIA using GeForce Experience.  I wasn't willing to roll back drivers to test this but I did do render tests on the latest driver with 2.81 with None, CUDA and Optix.

Blender Cycles Time to Render a Single Frame
  • 2.8 (Cuda?) = 90 Seconds
  • 2.81 (None) = 262 Seconds  <- This implies previous test on old driver wasn't using GPU.
  • 2.81 (Cuda) = 89 Seconds
  • 2.81 (Optix) =68 Seconds

The interesting result here is 2.81 using Optix. I'm seeing about a 25% reduction in render time which again is definitely worth having.


Picture
The scene being used for testing
Disclaimer: 
I used to work at NVIDIA :-)
0 Comments



Leave a Reply.

    David Coombes

    Making stuff

    Categories

    All
    3D Graphics
    3D Printing
    3D Scanning
    AI
    Blender
    Cycling
    Development
    Environment
    Futurism

    Archives

    February 2023
    November 2022
    April 2022
    February 2022
    January 2022
    February 2021
    January 2021
    November 2020
    May 2020
    April 2020
    March 2020
    February 2020
    December 2019
    November 2019
    September 2019
    August 2019
    July 2019
    January 2019
    December 2018
    October 2018
    August 2018
    June 2018
    April 2018
    March 2018
    February 2018
    January 2018
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    January 2017
    September 2016
    August 2016
    July 2016
    May 2016
    April 2016
    March 2016
    December 2015
    November 2015
    August 2015
    July 2015
    June 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014

    RSS Feed