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.

All of our benchmark results can also be found in our benchmark engine, Bench.

Corona 1.3: link

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: link

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

This is one multi-threaded test where the 8-core Skylake-based Intel processor wins against the new AMD Ryzen 7 2700X; the variable threaded nature of Blender means that the mesh architecture and memory bandwidth work well here. On a price/parity comparison, the Ryzen 7 2700X easily takes the win from the top performers. Users with the Core i7-6700K are being easily beaten by the Ryzen 5 2600.

LuxMark v3.1: Link

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++
Rendering: LuxMark CPU OpenCL

POV-Ray 3.7.1b4: link

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: link

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 SingleThreaded
Rendering: CineBench 15 MultiThreaded

Intel is still the single thread champion in benchmarks like CineBench, but it would appear that the Ryzen 7 2700X is now taking the lead in the multithreaded test.

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

545 Comments

View All Comments

  • eek2121 - Thursday, April 19, 2018 - link

    Their benchmarks are garbage? You are welcome to buy a 2700X and test for yourself. The benchmarks they used are built in for the most part to each game. It coincides pretty much with what I know of Ryzen, Coffee Lake, and Ryzen 2xxx.
  • AndersFlint - Thursday, April 19, 2018 - link

    While out of respect for the reviewer's hard work, I wouldn't describe the results as "garbage", they certainly don't match up with results from other publications.
  • ACE76 - Thursday, April 19, 2018 - link

    Yes, Anandtech's are honest and objective...I believe Tech Radar was comparing Coffee Lake OC'd to 5.2ghz vs Ryzen 2700x at 4.1ghz...the stock turbo alone hits 4.3ghz...they are slanting to benefit Intel...a 5.2ghz stable overclock on Coffee Lake alone is very hard to achieve and maybe 10-15% of CPUs can do it.
  • Luckz - Monday, April 23, 2018 - link

    I haven't really heard of anyone unable to reach 5 GHz.
  • SkyBill40 - Thursday, April 19, 2018 - link

    Well, golly gee... did the other reviewers use the *exact* setup as used here? No? Hmm... I guess that then makes your grouchy mcgrouchface missive not worth consideration then, no? If anyone is to not be taken seriously here, it's you.

    Typical ad hominem and burden of proof fallacies. Well done, Chris113q.
  • Flying Aardvark - Thursday, April 19, 2018 - link

    WRONG. AT has it right, these are properly patched systems. Heavy IO perf loss with Intel Meltdown patches has been well known for months. See top comment here. https://np.reddit.com/r/pcmasterrace/comments/7obo...
    Prove your claim that the data is incorrect or misleading in any way whatsoever, child.
  • RafaelHerschel - Thursday, April 19, 2018 - link

    One of the problems is that other reviewers see a less pronounced difference between the new AMD Ryzen CPU's and the older ones. Most reviewers claim that they have tested with all available patches in place.

    Your conclusion that AT has it right is based on what? Your belief that AT can't make mistakes? Maybe there is a logical explanation, but for now, it seems that AT might have done something wrong.
  • Flying Aardvark - Friday, April 20, 2018 - link

    I have evidence to backup my claim, users with no motivation to mislead agree with AT, and did months ago. You have no evidence, simply butthurt. Good luck.
  • boozed - Thursday, April 19, 2018 - link

    Let's ask a total jerk from the internet what he thinks.
  • aliquis - Thursday, April 19, 2018 - link

    They definitely used slower memory. Don't know if that's the thing. Don't know what fps others get in the same games and settings. Otherwise maybe it's ASUS doing special tricks like with MCE before or have better memory timits or can use some trick to get similar of precision boost overdrive already. Or a software mistake.

    Sweclockers is the best for game performance. They do 720p medium so the gpu limits will be smallest there.

Log in

Don't have an account? Sign up now