Benchmarking Performance: CPU Rendering Tests

Rendering tests are a long-time favorite of reviewers and benchmarkers, as the code used by rendering packages is usually highly optimized to squeeze every little bit of performance out. Sometimes rendering programs end up being heavily memory dependent as well - when you have that many threads flying about with a ton of data, having low latency memory can be key to everything. Here we take a few of the usual rendering packages under Windows 10, as well as a few new interesting benchmarks.

Corona 1.3

Corona is a standalone package designed to assist software like 3ds Max and Maya with photorealism via ray tracing. It's simple - shoot rays, get pixels. OK, it's more complicated than that, but the benchmark renders a fixed scene six times and offers results in terms of time and rays per second. The official benchmark tables list user submitted results in terms of time, however I feel rays per second is a better metric (in general, scores where higher is better seem to be easier to explain anyway). Corona likes to pile on the threads, so the results end up being very staggered based on thread count.

Rendering: Corona Photorealism

Blender 2.78

For a render that has been around for what seems like ages, Blender is still a highly popular tool. We managed to wrap up a standard workload into the February 5 nightly build of Blender and measure the time it takes to render the first frame of the scene. Being one of the bigger open source tools out there, it means both AMD and Intel work actively to help improve the codebase, for better or for worse on their own/each other's microarchitecture.

Rendering: Blender 2.78

LuxMark

As a synthetic, LuxMark might come across as somewhat arbitrary as a renderer, given that it's mainly used to test GPUs, but it does offer both an OpenCL and a standard C++ mode. In this instance, aside from seeing the comparison in each coding mode for cores and IPC, we also get to see the difference in performance moving from a C++ based code-stack to an OpenCL one with a CPU as the main host.

Rendering: LuxMark CPU C++

POV-Ray 3.7b3

Another regular benchmark in most suites, POV-Ray is another ray-tracer but has been around for many years. It just so happens that during the run up to AMD's Ryzen launch, the code base started to get active again with developers making changes to the code and pushing out updates. Our version and benchmarking started just before that was happening, but given time we will see where the POV-Ray code ends up and adjust in due course.

Rendering: POV-Ray 3.7

Cinebench R15

The latest version of CineBench has also become one of those 'used everywhere' benchmarks, particularly as an indicator of single thread performance. High IPC and high frequency gives performance in ST, whereas having good scaling and many cores is where the MT test wins out.

Rendering: CineBench 15 MultiThreaded

Rendering: CineBench 15 SingleThreaded

 

Benchmarking Performance: CPU System Tests Benchmarking Performance: CPU Web Tests
Comments Locked

264 Comments

View All Comments

  • Gastec - Sunday, August 20, 2017 - link

    The Ryzen 1600X has the same theoretical frequencies as 1800X (on paper) minus 2 cores. Both Ryzen 1700X and 1700 have lower frequencies than 1600X. As to why the 1600X shows slightly better results than 1800X in some single-core tests it's probably due to a combination of lower power consumption(less heat) XFR and binning.
    Read this: http://www.anandtech.com/show/11244/the-amd-ryzen-...
  • dstephens80 - Monday, August 14, 2017 - link

    All, I have come across something interesting and wondering if it is only me. I just received my 7820x and was playing around with overclocking and I have to question Intel's claim that the CPUs are "Fully Unlocked". Using an Asus Strix-E X299 MB I adjusted my overclock to 4.6Ghz and then booted successfully and started my stress testing. I noticed my clock speed was bouncing between 4.3 and 4.6 so I thought maybe speedstep was interfering and went into BIOS and turned off SpeedStep, TurboBoost and C-states. When I booted back up I received an error for the TurboBoost utility (expected) but my speed was at the stock 3.6Ghz and the Intel Extreme Utility showed the same but also showed my multiplier should be set at 46. I went back into BIOS and enabled "TurboBoost" and upon reboot CPUz/Intel utility both showed speed at 4.6Ghz. My issue with the "Fully Unlocked" claim is that an OC should not be dependent on a software driver. I have confimed this by the fact that when I boot Linux the OC is not applied.
  • leeymcj - Sunday, September 3, 2017 - link

    I have a question, so all the cores are equipped with dedicated AVX register? (cost ~15% of area for each of them)
  • gogi95 - Wednesday, September 27, 2017 - link

    what is replacement algorithm used in Intel core i9?

Log in

Don't have an account? Sign up now