![]() It looks like maybe the games are not needing the Shader counts as much as the games may be liking any extra L2 cache that Titan V can have available to keep and mamory access latency issues to a minimum. I’d like to see Titan V’s shader core utilization rates and that average closk rate is not too bad on Titan V and I wish there where some Titan Xp average clock rates for comparsion. Titan V’s lower clocks base/boost clocks are more than made up for by other factors such as more shader cores/L2 cache and higher texture throughput. Titan V’s shader counts are overkill for gaming and my money is on the Titan V’s larger L2 cache helping to lower the latency because Titan V’s ROP counts are the same as Titan Xp’s ROP counts. Titan V has more TMUs than the Titan Xp and those 320 TMUs on Titan V sure up Nvidia’s Texture Fill Rates even relative to AMD’s Vega Micro-Arch based Vega 64/56 SKUs. So is it Titan V’s HBM2 higher effective memory bandwidth and much wider HBM2 interface that is giving Titan V the most help in gaming or is it the larger cache on the Titan V relative to the Titan XP that is really helping keep the latency to a minimum. Wikipedia lists the L2 cache size on the Titan V as 4608KB and the Titan Xp’s L2 as 4096 KB and the Titan Xp has 96 ROPs as does the Titan V have 96 ROPs. Replyĩ6 ROPs for Titan V and a little more memory bandwidth over the the Titan Xp and a lot more shaders. So maybe a dual Vega 64 or even a Dual Vega 20 for the professional markets that makes more use of the Infinity Fabric that the Fiji XT Radeon Pro Duo did not have the option of makeing use of. ![]() ![]() That Radeon Pro Duo(Fiji XT) has 2× 4096:256:64 shaders:TMUs:ROPs for pleny of compute power and non gaming graphics rendering power. And that gives AMD the option of wiring up some Dual GPU DIE on one PCIe card designs that can scale up and look to any software/driver just like a single bigger logical GPU.ĪMD does not have to wait for Navi to go modular it’s just that Navi will be using more smaller GPU die chiplets that can be fabbed with very high yields and give AMD a finer grained ability to scale up GPU power from mobile to flagship using a smaller modular GPU common Die design. So any Vega refresh dies on 12nm, including Vega 20 with is higher FP 64 number crunching will have already had the Infinity Fabric IP since the first Vega SKUs where introduced. Navi is more about that scalable Zen/Zeppelin sort of modular design taken to the next level and the Infinity Fabric IP is in all of AMD’s new Zen/Volta products currently. Navi is more about producing scalable GPUs from smaller GPU DIEs that can be wired up Infinity Fabric style to look like one big single GPU more than Navi is that much of a GPU micro-arch change over the Vega GPU micro-arch. Look at how the Infinity fabric ties all those Zen/Zeppelin dies together on TR/Epyc and that part of Navi is already here. And Vega speaks the Infinity Fabric so any dual GPU dies on a single PCIe card configurations may not need to worry about any software/driver/API CF support as 2 GPU dies wired up via the Infinity Fabric IP would look to the software/drivers as a single monolithic logical GPU. Vega 20 is going to be even more DP FP heavy with a 1/2 DP FP to SP FP ratio. ![]() AMD can always do a dual GPU die on one PCIe card configuration with Vega.
0 Comments
Leave a Reply. |