Compute

Shifting gears, we have our look at compute performance.

As we outlined earlier, GTX Titan X is not the same kind of compute powerhouse that the original GTX Titan was. Make no mistake, at single precision (FP32) compute tasks it is still a very potent card, which for consumer level workloads is generally all that will matter. But for pro-level double precision (FP64) workloads the new Titan lacks the high FP64 performance of the old one.

Starting us off for our look at compute is LuxMark3.0, the latest version of the official benchmark of LuxRender 2.0. LuxRender’s GPU-accelerated rendering mode is an OpenCL based ray tracer that forms a part of the larger LuxRender suite. Ray tracing has become a stronghold for GPUs in recent years as ray tracing maps well to GPU pipelines, allowing artists to render scenes much more quickly than with CPUs alone.

Compute: LuxMark 3.0 - Hotel

While in LuxMark 2.0 AMD and NVIDIA were fairly close post-Maxwell, the recently released LuxMark 3.0 finds NVIDIA trailing AMD once more. While GTX Titan X sees a better than average 41% performance increase over the GTX 980 (owing to its ability to stay at its max boost clock on this benchmark) it’s not enough to dethrone the Radeon R9 290X. Even though GTX Titan X packs a lot of performance on paper, and can more than deliver it in graphics workloads, as we can see compute workloads are still highly variable.

For our second set of compute benchmarks we have CompuBench 1.5, the successor to CLBenchmark. CompuBench offers a wide array of different practical compute workloads, and we’ve decided to focus on face detection, optical flow modeling, and particle simulations.

Compute: CompuBench 1.5 - Face Detection

Compute: CompuBench 1.5 - Optical Flow

Compute: CompuBench 1.5 - Particle Simulation 64K

Although GTX Titan X struggled at LuxMark, the same cannot be said for CompuBench. Though the lead varies with the specific sub-benchmark, in every case the latest Titan comes out on top. Face detection in particular shows some massive gains, with GTX Titan X more than doubling the GK110 based GTX 780 Ti's performance.

Our 3rd compute benchmark is Sony Vegas Pro 13, an OpenGL and OpenCL video editing and authoring package. Vegas can use GPUs in a few different ways, the primary uses being to accelerate the video effects and compositing process itself, and in the video encoding step. With video encoding being increasingly offloaded to dedicated DSPs these days we’re focusing on the editing and compositing process, rendering to a low CPU overhead format (XDCAM EX). This specific test comes from Sony, and measures how long it takes to render a video.

Compute: Sony Vegas Pro 13 Video Render

Traditionally a benchmark that favors AMD, GTX Titan X closes the gap some. But it's still not enough to surpass the R9 290X.

Moving on, our 4th compute benchmark is FAHBench, the official Folding @ Home benchmark. Folding @ Home is the popular Stanford-backed research and distributed computing initiative that has work distributed to millions of volunteer computers over the internet, each of which is responsible for a tiny slice of a protein folding simulation. FAHBench can test both single precision and double precision floating point performance, with single precision being the most useful metric for most consumer cards due to their low double precision performance. Each precision has two modes, explicit and implicit, the difference being whether water atoms are included in the simulation, which adds quite a bit of work and overhead. This is another OpenCL test, utilizing the OpenCL path for FAHCore 17.

Compute: Folding @ Home: Explicit, Single Precision

Compute: Folding @ Home: Implicit, Single Precision

Folding @ Home’s single precision tests reiterate just how powerful GTX Titan X can be at FP32 workloads, even if it’s ostensibly a graphics GPU. With a 50-75% lead over the GTX 780 Ti, the GTX Titan X showcases some of the remarkable efficiency improvements that the Maxwell GPU architecture can offer in compute scenarios, and in the process shoots well past the AMD Radeon cards.

Compute: Folding @ Home: Explicit, Double Precision

On the other hand with a native FP64 rate of 1/32, the GTX Titan X flounders at double precision. There is no better example of just how much the GTX Titan X and the original GTX Titan differ in their FP64 capabilities than this graph; the GTX Titan X can’t beat the GTX 580, never mind the chart-topping original GTX Titan. FP64 users looking for an entry level FP64 card would be well advised to stick with the GTX Titan Black for now. The new Titan is not the prosumer compute card that was the old Titan.

Wrapping things up, our final compute benchmark is an in-house project developed by our very own Dr. Ian Cutress. SystemCompute is our first C++ AMP benchmark, utilizing Microsoft’s simple C++ extensions to allow the easy use of GPU computing in C++ programs. SystemCompute in turn is a collection of benchmarks for several different fundamental compute algorithms, with the final score represented in points. DirectCompute is the compute backend for C++ AMP on Windows, so this forms our other DirectCompute test.

Compute: SystemCompute v0.5.7.2 C++ AMP Benchmark

With the GTX 980 already performing well here, the GTX Titan X takes it home, improving on the GTX 980 by 31%. Whereas GTX 980 could only hold even with the Radeon R9 290X, the GTX Titan X takes a clear lead.

Overall then the new GTX Titan X can still be a force to be reckoned with in compute scenarios, but only when the workloads are FP32. Users accustomed to the original GTX Titan’s FP64 performance on the other hand will find that this is a very different card, one that doesn’t live up to the same standards.

Synthetics Power, Temperature, & Noise
Comments Locked

276 Comments

View All Comments

  • Dug - Thursday, March 19, 2015 - link

    Thank you for pointing this out.
  • chizow - Monday, March 23, 2015 - link

    Uh, they absolutely do push 4GB, its not all for the framebuffer but they use it as a texture cache that absolutely leads to a smoother gaming experience. I've seen SoM, FC4, AC:Unity all use the entire 4GB on my 980 at 1440p Ultra settings (textures most important ofc) even without MSAA.

    You can optimize as much as you like but if you can keep texture buffered locally it is going to result in a better gaming experience.

    And for 780Ti owners not being happy, believe what you like, but these are the folks jumping to upgrade even to 980 because that 3GB has crippled the card, especially at higher resolutions like 4K. 780Ti beats 290X in everything and every resolution, until 4K.

    https://www.google.com/?gws_rd=ssl#q=780+ti+3gb+no...
  • FlushedBubblyJock - Thursday, April 2, 2015 - link

    Funny how 3.5GB wass just recently a kickk to the insufficient groin, a gigantic and terrible lie, and worth a lawsuit due to performance issues... as 4GB was sorely needed, now 4GB isn't used....

    Yes 4GB isn't needed. It was just 970 seconds ago, but not now !
  • DominionSeraph - Tuesday, March 17, 2015 - link

    You always pay extra for the privilege of owning a halo product.
    Nvidia already rewrote the pricing structure in the consumer's favor when they released the GTX 970 -- a card with $650 performance -- at $329. You can't complain too much that they don't give you the GTX 980 for $400. If you want above the 970 you're going to pay for it. And Nvidia has hit it out of the ballpark with the Titan X. If Nvidia brought the high end of Maxwell down in price AMD would pretty much be out of business considering they'd have to sell housefire Hawaii at $150 instead of being able to find a trickle of pity buyers at $250.
  • MapRef41N93W - Tuesday, March 17, 2015 - link

    Maxwell architecture is not designed for FP64. Even the Quadro doesn't have it. It's one of the ways NVIDIA saved so much power on the same node.
  • shing3232 - Tuesday, March 17, 2015 - link

    I believe they could put FP64 into it if they want, but power efficiency is a good way to make ads.
  • MapRef41N93W - Tuesday, March 17, 2015 - link

    Would have required a 650mm^2 die which would have been at the limits of what can be done on TSMC 28nm node. Would have also meant a $1200 card.
  • MapRef41N93W - Tuesday, March 17, 2015 - link

    And the Quadro a $4000 card doesn't have it, so why would a $999 gaming card have it.
  • testbug00 - Tuesday, March 17, 2015 - link

    would it have? No. They could have given it FP64. Could they have given it FP64 without pushing the power and heat up a lot? Nope.

    the 390x silicon will be capable of over 3TFlop FP64 (the 390x probably locked to 1/8 performance, however) and will be a smaller chip than this. The price to pay will be heat and power. How much? Good question.
  • dragonsqrrl - Tuesday, March 17, 2015 - link

    Yes, it would've required a lot more transistors and die area with Maxwell's architecture, which relies on separate fp64 and fp32 cores. Comparing the costs associated with double precision performance directly to GCN is inaccurate.

Log in

Don't have an account? Sign up now