The AMD Ryzen 5 1600X vs Core i5 Review: Twelve Threads vs Four at $250
by Ian Cutress on April 11, 2017 9:00 AM ESTBenchmarking Performance: CPU System Tests
Our first set of tests is our general system tests. These set of tests are meant to emulate more about what people usually do on a system, like opening large files or processing small stacks of data. This is a bit different to our office testing, which uses more industry standard benchmarks, and a few of the benchmarks here are relatively new and different.
PDF Opening
First up is a self-penned test using a monstrous PDF we once received in advance of attending an event. While the PDF was only a single page, it had so many high-quality layers embedded it was taking north of 15 seconds to open and to gain control on the mid-range notebook I was using at the time. This put it as a great candidate for our 'let's open an obnoxious PDF' test. Here we use Adobe Reader DC, and disable all the update functionality within. The benchmark sets the screen to 1080p, opens the PDF to in fit-to-screen mode, and measures the time from sending the command to open the PDF until it is fully displayed and the user can take control of the software again. The test is repeated ten times, and the average time taken. Results are in milliseconds.
Opening PDFs using Adobe is significantly single threaded, hence why Intel takes the win here for the most part - the 7400 is slightly lower on frequency, enough for the 4.0 GHz Ryzen parts to push ahead.
FCAT Processing
One of the more interesting workloads that has crossed our desks in recent quarters is FCAT - the tool we use to measure stuttering in gaming due to dropped or runt frames. The FCAT process requires enabling a color-based overlay onto a game, recording the gameplay, and then parsing the video file through the analysis software. The software is mostly single-threaded, however because the video is basically in a raw format, the file size is large and requires moving a lot of data around. For our test, we take a 90-second clip of the Rise of the Tomb Raider benchmark running on a GTX 980 Ti at 1440p, which comes in around 21 GB, and measure the time it takes to process through the visual analysis tool.
Similarly, FCAT is single threaded as it analyzes frame-by-frame. The extra frequency helps Intel here.
3D Particle Movement v2.1
This is the latest version of the self-penned 3DPM benchmark. The goal of 3DPM is to simulate semi-optimized scientific algorithms taken directly from my doctorate thesis. Version 2.1 improves over 2.0 by passing the main particle structs by reference rather than by value, and decreasing the amount of double->float->double recasts the compiler was adding in. It affords a ~25% speed-up over v2.0, which means new data.
DigiCortex 1.20
Despite being a couple of years old, the DigiCortex software is a pet project for the visualization of neuron and synapse activity in the brain. The software comes with a variety of benchmark modes, and we take the small benchmark which runs a 32k neuron/1.8B synapse simulation. The results on the output are given as a fraction of whether the system can simulate in real-time, so anything above a value of one is suitable for real-time work. The benchmark offers a 'no firing synapse' mode, which in essence detects DRAM and bus speed, however we take the firing mode which adds CPU work with every firing.
Agisoft Photoscan 1.0
Photoscan stays in our benchmark suite from the previous version, however now we are running on Windows 10 so features such as Speed Shift on the latest processors come into play. The concept of Photoscan is translating many 2D images into a 3D model - so the more detailed the images, and the more you have, the better the model. The algorithm has four stages, some single threaded and some multi-threaded, along with some cache/memory dependency in there as well. For some of the more variable threaded workload, features such as Speed Shift and XFR will be able to take advantage of CPU stalls or downtime, giving sizeable speedups on newer microarchitectures.
Because parts of Photoscan are very multithreaded, such as the first stage, there's plenty of scope for the Ryzen CPUs to pull ahead here.
254 Comments
View All Comments
lefty2 - Tuesday, April 11, 2017 - link
Yeah, also with the RX 480 the i5 7400 scores better then i5 7600 (by a huge margin)! That makes no sensesharrken - Wednesday, April 12, 2017 - link
AdoredTV did a very interesting video about exactly this issue, called "Ryzen of the Tomb Raider". In pretty extensive testing they show that something is definitely wrong with Nvidia cards in DX12 on Tomb Raider.https://www.youtube.com/watch?v=0tfTZjugDeg
On a Ryzen 1800X system, crossfire RX 480's beat out an overclocked Titan X, 90fps on the 480's and only 80fps on a Titan X - which is just ridiculously wrong when you look at the relative GPU power.
Some other people have run more tests, and a similar thing is happening in The Division, so it seems highly likely that Nvidia has some strange issues somewhere along the line with DX12.
https://www.reddit.com/r/Amd/comments/62n813/inspi...
milli - Wednesday, April 12, 2017 - link
It's also happening in Battlefield 1, Deus Ex: MD & Total War: W.https://www.computerbase.de/2017-03/amd-ryzen-1800...
Are nVidia drivers not detecting Ryzen CPU's correctly or is it foul play?
mdw9604 - Thursday, April 13, 2017 - link
Poor AVX implementation /w AMD and the driver.milli - Thursday, April 13, 2017 - link
What has AVX to do with nVidia's DX12 drivers???bug77 - Tuesday, April 11, 2017 - link
Really great job not throwing intel power consumption in there for comparison. /sIan Cutress - Tuesday, April 11, 2017 - link
Mainly because that part of the discussion was purely to do with CCX arrangement and core loading.But sure, because you asked so nicely. /s They've been added.
bug77 - Tuesday, April 11, 2017 - link
Thanks.Phiro69 - Tuesday, April 11, 2017 - link
Could you comment on your Chromium Compile benchmark a bit; I'd like to use it as part of a pitch on why our compile farm needs replacing (e.g. "look what a $249 cpu can do").What OS did you build under, I'm guessing Windows 10 from your earlier statements in the full article?
Did you follow these directions for the most part? https://chromium.googlesource.com/chromium/src/+/m...
If so (and you used Windows 10), then you used Visual Studio? Which version and which license of VS?
Thanks! Great review!
Ian Cutress - Tuesday, April 11, 2017 - link
Win 10 x64 Pro v1607, Build 14393.953. VS Community 2015.3 with Win10 SDK. I bascially followed the instructions in that link. :)