Question Speculation: RDNA2 + CDNA Architectures thread

Page 100 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

uzzi38

Platinum Member
Oct 16, 2019
2,565
5,572
146
All die sizes are within 5mm^2. The poster here has been right on some things in the past afaik, and to his credit was the first to saying 505mm^2 for Navi21, which other people have backed up. Even still though, take the following with a pich of salt.

Navi21 - 505mm^2

Navi22 - 340mm^2

Navi23 - 240mm^2

Source is the following post: https://www.ptt.cc/bbs/PC_Shopping/M.1588075782.A.C1E.html
 

PhoBoChai

Member
Oct 10, 2017
119
389
106
You guys with your back & forth about leakers and tech tubers make this tech forum have the same quality (LOW) as reddit. Basically if you don't believe or believe a leaker, leave it be, ppl can view and decide for themselves, there's no need to get so side tracked and it becomes a discussion over personalities instead of what we're all here for: GPU tech.
 

Vixis Rei

Junior Member
Jul 4, 2020
13
16
41
Coreteks's leak has been declared fake by leaker Kittyyyuuko


EDIT: Maybe it's referred to the picture itself, but that was already declared as a photoshop edit by the author of the video

I wonder if kitty knows it's modified / photoshopped? In this case just saying it's fake isn't helpful. Doubt kitty would tell how similar it is to the real thing if they do know.
 

ModEl4

Member
Oct 14, 2019
71
33
61
In Anandtech's coverage of Hot Chips Series X event, in the interview section there was a reply from the Microsoft team in a question, and they said that the ray tracing portion is only 5% of the GPU transistor budget. The thing is that I cannot find it anymore, does anyone else remembers this?
 
May 17, 2020
122
233
86
I wonder if kitty knows it's modified / photoshopped? In this case just saying it's fake isn't helpful. Doubt kitty would tell how similar it is to the real thing if they do know.
The part with caps has been taken from NAVI10 but it has modified too the QR code on the corner, it's weird and i don't know why

Why it not showing the board by hiding some elements ?
 

moinmoin

Diamond Member
Jun 1, 2017
4,933
7,619
136
In Anandtech's coverage of Hot Chips Series X event, in the interview section there was a reply from the Microsoft team in a question, and they said that the ray tracing portion is only 5% of the GPU transistor budget. The thing is that I cannot find it anymore, does anyone else remembers this?
You mean this?
202008180228051_575px.jpg


I don't remember any more specific transistor budget being mentioned.
 

kurosaki

Senior member
Feb 7, 2019
258
250
86
Wonder how they implement the RTRT. Is one ray needed per pixel? That grows to quite many gigarays pretty fast. 1440x2560x60fps is like 220 something gigapixles/second. If light bounces three times before it is rendered as a pixel, well that is 660 giga-rays needed to be calculated per sec. Must be something that does not need a setup that isn't one ray per pixel anyways. Anyone knows how it kind of works behind the scenes?
 

Konan

Senior member
Jul 28, 2017
360
291
106
Wonder how they implement the RTRT. Is one ray needed per pixel? That grows to quite many gigarays pretty fast. 1440x2560x60fps is like 220 something gigapixles/second. If light bounces three times before it is rendered as a pixel, well that is 660 giga-rays needed to be calculated per sec. Must be something that does not need a setup that isn't one ray per pixel anyways. Anyone knows how it kind of works behind the scenes?
Got this to go off... The ratio for texture unit v RT is 1:1 (edit)
DEF08BC8-12D5-41B6-85D5-52C51656CAFD.jpeg
There have also been a few rumours that say not all CU throughput is there when RT is happening. I.e. around 20% of CUs focused on RT efforts.
Similar to how doubling of CUDA cores with ampere doesn’t give a doubling of perf. So like 80CU is not 80CU of throughput when RT happening. That said who knows just a few rumors on the grapevine...I’d take those with some salt but not much else to go on
 
Last edited:

Asterox

Golden Member
May 15, 2012
1,026
1,775
136
You guys with your back & forth about leakers and tech tubers make this tech forum have the same quality (LOW) as reddit. Basically if you don't believe or believe a leaker, leave it be, ppl can view and decide for themselves, there's no need to get so side tracked and it becomes a discussion over personalities instead of what we're all here for: GPU tech.

My favorite leaker is David Wang, but he is mostly ignored by everyone. :relieved:

 

maddie

Diamond Member
Jul 18, 2010
4,722
4,626
136
Wonder how they implement the RTRT. Is one ray needed per pixel? That grows to quite many gigarays pretty fast. 1440x2560x60fps is like 220 something gigapixles/second. If light bounces three times before it is rendered as a pixel, well that is 660 giga-rays needed to be calculated per sec. Must be something that does not need a setup that isn't one ray per pixel anyways. Anyone knows how it kind of works behind the scenes?
It's 220 megapixels/sec for that resolution & framerate.
 
  • Like
Reactions: kurosaki

uzzi38

Platinum Member
Oct 16, 2019
2,565
5,572
146
No one can prove either way. Accept, they are persistent. Maybe where there is smoke there is fire for a hybrid architectural RT approach...

Yeah they can, they can just go rewatch the Series X HotChips presentation, the Road to PS5 presentation, or alternatively go patent digging.

It's not difficult to filter that rumour out and laugh about it.

In the first place, how did nobody realise that dynamically adjusting CUs for performing BVH traversal and intersection is NOT HARDWARE BASED RAYTRACING.
 

ModEl4

Member
Oct 14, 2019
71
33
61
Texture/Ray-box ratio is 1:1
Texture/Ray-triangle ratio is 4:1
It's in the MS slides if you do the calculations.
The fun thing would be, if there was a sci-fi (lol) deterministic correlation between actual in game Ray-triangle performance vs theoretical max like we have for actual real triangle output vs theoretical max like in PS5 unreal engine 5 demo for example. 19-20 million triangles per frame (30fps) at 2230MHz so around 1/15 - 1/16 of the theoretical max (4 primitives) , this would give for PS5 Ray-triangle (if we calculate with 1/16) around 5Grays/s actual performance (RTX 2060 level?) and for Xbox SeriesX around 6Grays/s actual performance. Now that is an analysis worthy of the Sheldon award🤪
 
  • Love
Reactions: PhoBoChai

Konan

Senior member
Jul 28, 2017
360
291
106
Hey I'm not arguing, just playing devils advocate. Ok here is a patent (already had read it last week when it was published)
Ray Intersection Unit inside of the CU, patent describes the functions of RT. When I posted it was that there have been persistent rumors regarding CU throughput when RT is involved. Patent is inconclusive on performance but I still feel the questions is open.

1601841408702.png 1601841607636.png

1601840917813.png
1601841498230.png
 
Last edited:

Ajay

Lifer
Jan 8, 2001
15,332
7,792
136
Yeah they can, they can just go rewatch the Series X HotChips presentation, the Road to PS5 presentation, or alternatively go patent digging.

It's not difficult to filter that rumour out and laugh about it.

In the first place, how did nobody realise that dynamically adjusting CUs for performing BVH traversal and intersection is NOT HARDWARE BASED RAYTRACING.
Yes it is. It’s just that the hardware ray tracing isn’t done by a fixed function unit.
 

soresu

Platinum Member
Dec 19, 2014
2,617
1,812
136
around 5Grays/s actual performance (RTX 2060 level?)
I'm high suspicious over the figures nVidia supplied for gigarays per second on their RTX 2000 cards - considering they are fine with giving tensor sparse calculation numbers of equivalent to n TFLOPS rather than exact figures I do not put it past them to fudge the numbers on gigarays /s to push 'RTX' in its infancy.

Considering the backlash against the lackluster performance of RTX early on it seems like a likely strategy to stave off especially bad PR until they got chunkier cards and better DLSS out the door.
 

Hans Gruber

Platinum Member
Dec 23, 2006
2,092
1,065
136
Here is the problem AMD will face in November. If Big Navi is not as good as the 3080 and you have to start factoring in the power savings over Nvidia. Then you combine the release of the two new consoles from Sony and Microsoft. People will question buying any AMD or Nvidia cards because of cost compared to the new consoles. I realize that most if not all here are PC gamers. But there is a large percentage of kids who would put off building a new PC or upgrading their graphics cards when the new consoles are released.

With that said I am either getting the 3070 or one of the big Navi variants.
 
  • Like
Reactions: Tlh97 and kurosaki

ModEl4

Member
Oct 14, 2019
71
33
61
I'm high suspicious over the figures nVidia supplied for gigarays per second on their RTX 2000 cards - considering they are fine with giving tensor sparse calculation numbers of equivalent to n TFLOPS rather than exact figures I do not put it past them to fudge the numbers on gigarays /s to push 'RTX' in its infancy.

Considering the backlash against the lackluster performance of RTX early on it seems like a likely strategy to stave off especially bad PR until they got chunkier cards and better DLSS out the door.
I was just messing around, no need to analyze it too much😉 Maybe Nvidia numbers are overstated, probably, I don't know, but you have to consider also that the 5Grays/s actual number I came with, it has the necessary condition that each and every CU will do only Ray ops and zero Texture ops, each CU cannot perform at the same time 4 texture and 4 ray ops if I'm not mistaken.
 

PhoBoChai

Member
Oct 10, 2017
119
389
106
I was just messing around, no need to analyze it too much😉 Maybe Nvidia numbers are overstated, probably, I don't know, but you have to consider also that the 5Grays/s actual number I came with, it has the necessary condition that each and every CU will do only Ray ops and zero Texture ops, each CU cannot perform at the same time 4 texture and 4 ray ops if I'm not mistaken.

You never go by NV's claims, they have proven over the many years, it's a lot of marketing fluff.

As an example, there's an UE RT demo, just a simple small puddle of water reflection, and a 2060S is crippled in perf running it. There's not a chance any of the Turing GPUs can do the UE5 PS5 demo at 30 FPS.

RDNA 2 TMUs do 4 RT ops or texture ops however, texturing steps don't necessarily overlap lighting steps.

ps. When you calculate triangles in the scene and derive the gigaray/s, you have to factor in multiple bounces.
 

PhoBoChai

Member
Oct 10, 2017
119
389
106
Hey I'm not arguing, just playing devils advocate. Ok here is a patent (already had read it last week when it was published)
Ray Intersection Unit inside of the CU, patent describes the functions of RT. When I posted it was that there have been persistent rumors regarding CU throughput when RT is involved. Patent is inconclusive on performance but I still feel the questions is open.

View attachment 31100 View attachment 31102

RT always initiates first on the SIMD units. Devs call for a regular shader, which contains the ray/bvh data, that gets forwarded to the fixed function units to handle the bvh traversal & intersection testing.

You can even read RTX Ampere's whitepaper, NV does the same RT initialization in their cuda cores.

Not sure why ppl are even taking the 20/80 CU dedicated to RT seriously given both MS & Sony info reveal have dedicated RT hw units in RDNA 2.