TU117: Tiny Turing

Before we take a look at the Zotac card and our benchmark results, let’s take a moment to go over the heart of the GTX 1650: the TU117 GPU.

TU117 is for most practical purposes a smaller version of the TU116 GPU, retaining the same core Turing feature set, but with fewer resources all around. Altogether, coming from the TU116 NVIDIA has shaved off one-third of the CUDA cores, one-third of the memory channels, and one-third of the ROPs, leaving a GPU that’s smaller and easier to manufacture for this low-margin market.

Still, at 200mm2 in size and housing 4.7B transistors, TU117 is by no means a simple chip. In fact, it’s exactly the same die size as GP106 – the GPU at the heart of the GeForce GTX 1060 series – so that should give you an idea of how performance and transistor counts have (slowly) cascaded down to cheaper products over the last few years.

Overall, NVIDIA’s first outing with their new GPU is an interesting one. Looking at the specs of the GTX 1650 and how NVIDIA has opted to price the card, it’s clear that NVIDIA is holding back a bit. Normally the company launches two low-end cards at the same time – a card based on a fully-enabled GPU and a cut-down card – which they haven’t done this time. This means that NVIDiA is sitting on the option of rolling out a fully-enabled TU117 card in the future if they want to.

By the numbers, the actual CUDA core count differences between GTX 1650 and a theoretical fully-enabled GTX 1650 Ti are quite limited – to the point where I doubt a few more CUDA cores alone would be worth it – however NVIDIA also has another ace up its sleeve in the form of GDDR6 memory. If the conceptually similar GTX 1660 Ti is anything to go by, a fully-enabled TU117 card with a small bump in clockspeeds and 4GB of GDDR6 could probably pull far enough ahead of the vanilla GTX 1650 to justify a new card, perhaps at $179 or so to fill NVIDIA’s current product stack gap.

The bigger question is where performance would land, and if it would be fast enough to completely fend off the Radeon RX 570. Despite the improvements over the years, bandwidth limitations are a constant challenge for GPU designers, and NVIDIA’s low-end cards have been especially boxed in. Coming straight off of standard GDDR5, the bump to GDDR6 could very well put some pep into TU117’s step. But the price sensitivity of this market (and NVIDIA’s own margin goals) means that it may be a while until we see such a card; GDDR6 memory still fetches a price premium, and I expect that NVIDIA would like to see this come down first before rolling out a GDDR6-equipped TU117 card.

Turing’s Graphics Architecture Meets Volta’s Video Encoder

While TU117 is a pure Turing chip as far as its core graphics and compute architecture is concerned, NVIDIA’s official specification tables highlight an interesting and unexpected divergence in related features. As it turns out, TU117 has incorporated an older version of NVIDIA’s NVENC video encoder block than the other Turing cards. Rather than using the Turing block, it uses the video encoding block from Volta.

But just what does the Turing NVENC block offer that Volta’s does not? As it turns out, it’s just a single feature: HEVC B-frame support.

While it wasn’t previously called out by NVIDIA in any of their Turing documentation, the NVENC block that shipped with the other Turing cards added support for B(idirectional) Frames when doing HEVC encoding. B-frames, in a nutshell, are a type of advanced frame predication for modern video codecs. Notably, B-frames incorporate information about both the frame before them and the frame after them, allowing for greater space savings versus simpler uni-directional P-frames.

I, P, and B-Frames (Petteri Aimonen / PD)

This bidirectional nature is what make B-frames so complex, and this especially goes for video encoding. As a result, while NVIDIA has supported hardware HEVC encoding for a few generations now, it’s only with Turing that they added B-frame support for that codec. The net result is that relative to Volta (and Pascal), Turing’s NVENC block can achieve similar image quality with lower bitrates, or conversely, higher image quality at the same bitrate. This is where a lot of NVIDIA’s previously touted “25% bitrate savings” for Turing come from.

Past that, however, the Volta and Turing NVENC blocks are functionally identical. Both support the same resolutions and color depths, the same codecs, etc, so while TU117 misses out on some quality/bitrate optimizations, it isn’t completely left behind. Total encoder throughput is a bit less clear, though; NVIDIA’s overall NVENC throughput has slowly ratcheted up over the generations, in particular so that their GPUs can serve up an ever-larger number of streams when being used in datacenters.

Overall this is an odd difference to bake into a GPU when the other 4 members of the Turing family all use the newer encoder, and I did reach out to NVIDIA looking for an explanation for why they regressed on the video encoder block. The answer, as it turns out, came down to die size: NVIDIA’s engineers opted to use the older encoder to keep the size of the already decently-sized 200mm2 chip from growing even larger. Unfortunately NVIDIA isn’t saying just how much larger Turing’s NVENC block is, so it’s impossible to say just how much die space this move saved. However, that the difference is apparently enough to materially impact the die size of TU117 makes me suspect it’s bigger than we normally give it credit for.

In any case, the impact to GTX 1650 will depend on the use case. HTPC users should be fine as this is solely about encoding and not decoding, so the GTX 1650 is as good for that as any other Turing card. And even in the case of game streaming/broadcasting, this is (still) mostly H.264 for compatibility and licensing reasons. But if you fall into a niche area where you’re doing GPU-accelerated HEVC encoding on a consumer card, then this is a notable difference that may make the GTX 1650 less appealing than the TU116-powered GTX 1660.

The NVIDIA GeForce GTX 1650 Review: Featuring ZOTAC Meet the ZOTAC GeForce GTX 1650 OC


View All Comments

  • nevcairiel - Saturday, May 4, 2019 - link

    A P-Frame (Predictive Frame) by definition is only in one direction - backwards. B-Frames (Bidirectional Predictive Frame) are allowed in both directions. This is an import distinction because it matters in which order those frames are put into the encoded video. "Future" frames of course need to be send first, or you can't use them for prediction.

    Thats where pattern like "IPBBB" come from. You start with a single I frame, a single P frame referencing that I frame (the P might be shown after some B frames), and then an array of B frames that reference both the I and P frames - and possibly each other.

    P and B frames are otherwise identical in how they work. Both contain motion vectors and entropy data to correct the interpolation.

    Also note that H264 already supported up to 16 reference frames for interpolation. Its called bidirectional not because its two frames, but two directions - past and future.
  • Opencg - Friday, May 3, 2019 - link

    please include fortnight average fps over 10 hour playtime. for all cards. all on the same patch. thx Reply
  • Bulat Ziganshin - Friday, May 3, 2019 - link

    The "NVIDIA is holding back a bit" part is duplicated on pages 1 and 2 Reply
  • Ryan Smith - Friday, May 3, 2019 - link

    Whoops. That was meant to get excised when I rearranged the article. Thanks! Reply
  • eva02langley - Friday, May 3, 2019 - link

    This card shouldn't exist.

    R7 was making sense because it was cheaper than a 2080, however this is more expensive than a RX 570... AND WEAKER!
  • Oxford Guy - Saturday, May 4, 2019 - link

    It apparently exists for the GTX 960 buyers (the people who don't do their homework). Reply
  • eek2121 - Friday, May 3, 2019 - link

    In before 1650ti. ;) Reply
  • AshlayW - Friday, May 3, 2019 - link

    Wow. This card makes no sense. Go watch hardware unboxed's video where he conveniently shoots down the "power efficiency" argument. It's a load of rubbish, there is absolutely no reason to buy this card over even the 4GB 570, for any new gaming build. This review tried so hard to paint this turd in a positive light, continually underscoring AMD's "technological disadvantages" and "thin profit margin". P20 isn't even that much bigger than TU117 also.

    I'm sorry I just feel it is too friendly to nvidia and doesn't criticize this terrible product pricing enough. RX570 8GB pulse, fro sapphire is cooler running, quieter, vastly higher build quality, >10% faster, twice the vram and 135W board power, which is perfectly fine even for potato OEM builds anyway.

    Seriously, drop Ty efficiency arguy. This card is DOA at 149 because 570 killed it.

    1024 CC card at 130 bucks would've been passable, not this joke.
  • AshlayW - Friday, May 3, 2019 - link

    The 570 8Gb pulse is also the same price or cheaper than 1650, at least here in the UK. Forgot to mention that important point. Reply
  • AshlayW - Friday, May 3, 2019 - link

    Typos as I'm on my phone and I have fat fingers.

    Should read: "drop the efficiency argument"

Log in

Don't have an account? Sign up now