But when 4 GiByte graphics memory are starting to become too limiting for mainstream use, it is much easier to upgrade your system memory (best case: just add another 2 sticks) than your graphics memory.Not really. VRAM is VRAM, try using HBCC on a system with 4GB or 8GB System RAM and see how glorious this is compared to a 8GB VRAM card.
But when 4 GiByte graphics memory are starting to become too limiting for mainstream use, it is much easier to upgrade your system memory (best case: just add another 2 sticks) than your graphics memory.
It is risk production even though it will be used for chips going straight to market (same slide set as that slide is from sees GloFo considering H1/18 as risk production)That is also correct
Also, if Vega 32 is successor to RX 580 (36 CUs and ~1400 MHz), how faster will be? As it seems, GloFo will start production using 12LP in Q1 (not risk prod. as it was first thought), so if that one is used clocks will for sure be higher than current ones (1600 MHz). But I doubt that alone would be enough, even if Vega 11 reaches ~1800 MHz
How come this comes up now? It's been "multiGPU" in all their communication for a long time already (at least since 17.2.1 drivers in february, possibly earlier)Not 100% Vega-only, but nonetheless:
https://www.pcworld.com/article/322...brand-as-multi-gpu-gets-more-complicated.html
Apparently, Crossfire is not a marketing term that's gonna live on.
Why do people presume Vega 11 has to use HBM?
It's quite evident Vega heavily missed it's performance targets.1 - Substantially better power efficiency, which they need for laptop solutions.
2 - AMD has been praying the "4GB + HBCC is great!" idea, but all Vega 10 cards have at least 8GB (which makes HBCC practically useless for gaming for now).
3 - Vega 11 with GDDR5 would bring it too close to Polaris 10 cards, making it redundant.
I could see Vega 28/32 existing solely in laptops, offering e.g. GTX580 performance at ~75W power consumption. That would also go around the consumers who aren't willing to buy 4GB cards.
They already had all the time in the world to fix broken hardware with a respin. Vega10 passed the tapeout ages ago.Maybe they'll fix in Vega 11 what was/is broken in Vega 10
I can't speak for anyone else, but my GPU guy (Nate Oh) picked up on this when looking at AMD's announcement. This is the first time in some months where we've had any reason to look into CF, and.as AMD has never formally announced an end to the use of Crossfire, we've never noticed it before now.How come this comes up now? It's been "multiGPU" in all their communication for a long time already (at least since 17.2.1 drivers in february, possibly earlier)
People should really read the driver release notes, they're not that long and this has been in plain sight since last decemberI can't speak for anyone else, but my GPU guy (Nate Oh) picked up on this when looking at AMD's announcement. This is the first time in some months where we've had any reason to look into CF, and.as AMD has never formally announced an end to the use of Crossfire, we've never noticed it before now.
True, though crossfire/multigpu-switch happened long time before VegasSoo many so much more important things to keep track of. Like state of DSBR, Prim. Shaders, Launch Prices, Availability, HMB2 temps and packaging... Good for you if you never fell behind the curve on any of these.