![]() The 4930K I have though will go into my gaming system (R4E), since I don't mind the oc'ing fun, higher noise, etc., but it's not a system I'll use for converting video, for that I have a 6850K. Only thing I noticed so far is it didn't like me trying to set a 2133 RAM speed, but it worked ok at 1866 I can probably tighten the timings instead, currently just at 9/11/10/28/2T (GSkill 32GB kit, 8x4GB). For the target systems in question, it's a great solution. So, I'm very pleased with the 2680 v2 purchase, it's faster than my 3930K 4.8, runs with very low temps, much lower power draw, hence less heat, less fan noise and since it's not oc'd it'll be solidly reliable (this particular test system will eventually be in an office in India, so power/heat/reliability is critical). Note the following page on AT has a very handy summary of all the turbo bin levels: Testing on a P9X79 WS (all-core turbo of 3.1) gives a very impressive 15.44 for CB 11.5, and 1381 for CB R15 which is faster than a stock 8700K (for reference, the 1680 v2 scores 1230 for CB R15). By contrast, I bought several 2680 v2s for 165 UKP each. mapesdhs - Monday, Octolink Very interesting that the 1680 v2 is unlocked, I didn't know that.Īlas though, availability of the 1680 v2 is basically zero, whereas the 2680 v2 is very easy to find, and the cost of 1680 v2s which are available (outside the UK) is extremely high (typical BIN of 600 UKP, normal auction start price of 350 UKP, completed listings only shown for BIN items which were purchased for between 500 and 600 UKP).High IPC and high frequency gives performance in ST, whereas having good scaling and many cores is where the MT test wins out.ĬineBench R15 in single thread mode can take the Core i7-8700K by the horns and drag it to be the best performing chip ever tested. The latest version of CineBench has also become one of those 'used everywhere' benchmarks, particularly as an indicator of single thread performance. 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. 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. 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.Īnother regular benchmark in most suites, POV-Ray is another ray-tracer but has been around for many years. LuxMark v3.1: LinkĪs 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. 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.īlender seems to separate very nicely into core counts, with six cores from Intel matching eight cores from AMD. 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. Blender 2.78: linkįor a render that has been around for what seems like ages, Blender is still a highly popular tool. The frequency difference over the Skylake-X processor gives an extra +10% performance, but the 16-thread parts from AMD win out overall. With more threads on display, the Core i7-8700K gets ahead of the previous mainstream Core i7 parts. Corona likes to pile on the threads, so the results end up being very staggered based on thread count. 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). 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. Corona 1.3: linkĬorona is a standalone package designed to assist software like 3ds Max and Maya with photorealism via ray tracing. Here we take a few of the usual rendering packages under Windows 10, as well as a few new interesting benchmarks.Īll of our benchmark results can also be found in our benchmark engine, Bench. 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. 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. Benchmarking Performance: CPU Rendering Tests
0 Comments
Leave a Reply. |