See this? It was released months ago. This is AMD's Vega,

>>59691679
it's shit

>1540MHz

Just like 1500+ Polaris on air right?

>>59691729
This isn't Polaris? Duh, different architecture, different pipeline and clocks, not very smart are you?

This card was already released in December, why are you arguing facts?

>>59691729
MI25 = 25 TFLOPS fp16 = 12.5 TFLOPS fp32 = ~1525 MHz on a 4096 ALU chip.

That's also on an enterprise part with a passive heatsink that relies on server fans to blow through it. Historically AMD sells consumer part with active cooling clocked 5-10% higher. Highest end Vega will almost certainly have 1600-1650ish clocks.

>>59691763
>why are you arguing facts?
They know that even just a Fury X at those clocks is devastating to 1080ti, as AMD's IPC is far higher than Nvidias at the moment.
Not to mention the biggest arch change for AMD since GCN rolled out 6 years ago.

So, you know, shut it down?

>>59691679
You know what this means? If they didn't increase the shader count from 28nm to 14nm, that means that the shaders are much bigger, ergo their IPC is notably higher.
Add to that a dramatic increase in clockspeed and this thing will be insane.

Honestly, the whole Pascal lineup outside of P100 felt like a stopgap to me, no ALU increase at all, just purely clockspeed, I expected more from the jump to 16nm FinFETs honestly.

P100 is impressive though, but GP102 and anything smaller felt underwhelming

>>59691925
those are some big shaders.

>>59691878
GCN's IPC is actually fractionally worse than Maxwell's, and Vega's play accordingly is more on efficiency than anything else.

Fiji had a ton of FLOPS that went underutilized or outright wasted due to a number of architectural shortcomings.

>>59691981
Actual arch change is costly and takes fuckload of time, see Vega. Also NVIDIA needs hardware async in Volta.

>>59692008
Yeah, but Nvidia already had notably bigger shaders than AMD did, this makes them roughly equal in size.

>>59691925
the shaders aren't bigger, the chip is just smaller

>>59692022
I had that lined up perfectly for you, how did you not say "For you."

>>59692018
The 480 keeps up with a 1060 with far lower clocks though?

>>59691981
Pascal has some neat tricks, what's the most impressive for me is that they managed to get good clock signal quality at those clocks, this is by no means a small feat, it's like IBM pushing 4.0GHz clocks on those POWER8 monsters, degradation happens at high clocks, this is a silicon issue though.

But at its core, Pascal is a higher clocked Maxwell, not a big arch change like Fermi > Kepler or Terascale > GCN was

>>59692149
Vega is AMD's next big architecture change while Volta is Nvidia's next big change, makes sense they're taking their time with it

>>59692036
4u

>>59692036
I'd like to keep memes out of any slight technical discussion as I still somewhat care about this board and its rapidly decaying post quality.

>>59692300
Too late, the moments over now - he ruined it.

>>59692319
>conso- I mean GPU wars
>board quality
fuck off /v/

>>59692048
and many more shaders

>>59692149
To add to this, high clockspeeds also have latency and precision hickups, this is why you don't see 4.5GHz low core Xeons for markets that strictly need ST performance and reliability is important.
But lower clocked with shitload of L3 cache (up to 60MB), yes 4 core Xeons with 60MB LLC

>>59692358
But they're at similar die sizes(some 5-10%?) so AMD's shaders should be far smaller.

>>59692378
That that should mean AMD's IPC per mm2 is higher, rather than saying their IPC per ALU is higher.

>>59692429
Technically that's right, but this is mostly nitpicking though, AMD's simple shaders aren't directly comparable to Nvidia's complex ones.

Still, this discussion came into being from the discussion of Vega having the same amount of ALUs as Fury X, which indicates a large IPC increase, and since the 1080ti is somewhere around 3600 CUDA cores, direct ALU to ALU comparison between AMD and Nvidia will be much easier now.

>>59692509
That is if Vega's diesize is around GP102's diesize.

>>59692544
It's a bit larger.

>>59692571
Even better, it has slightly more shaders with a bit larger die size, that should make this comparison even more direct since you're comparing ALUs of similar size.
Gp102 isn't exactly small though, and I haven't seen (big) Vega's size yet.

When we're on this topic, anyone know if AMD is putting a super fat scalar unit in their CUs in Vega while still mostly having vector ones? This would be pretty amazing thing.
I've seen a patent about it, but this would explain why this launch is taking this long

>>59692048
>The 480 keeps up with a 1060 with far lower clocks though?

The 480 is at rough parity with the 1060 but is 15% bigger, has 33% more RAM size/bandwidth, and uses 25% more power.

GCN is amazingly competitive for a 5 year old architecture, but AMD really needs Vega to be a big efficiency jump if it wants to even be competitive in the future.

>>59692758
Then again Polaris has near similar perf/watt as Fiji but it's at 14nm, so Polaris shouldn't really be a discussion on efficiency anything since AMD obviously prioritized cost on it than anything else.

>>59692792
I think I can give the answer to that, Polaris is for all intents and purposes a Hawaii cut in half with some frontend and I/O changes.
It's ALU array is not very dense and its caches and SRAM cells are neither low power or high performance.
Looking purely at chip design, someone must have made this while shitfaced, from a price standpoint, this thing is easy to fab and make, which I guess was AMD's market hook when they released this.

>>59692965
Also its low amount of fixed function units like ROPs is pretty telling.

File: ef863980c6d742d6be8285356a039ac7-3.png (382KB, 2666x1500px) Image search: [Google]

382KB, 2666x1500px

>>59692792
>>59692965
>>59693065
Polaris is not Fiji cut in half, it's Fiji with nearly half its shaders removed, which isn't the same thing.

>>59691713
my nama jeff

File: AMD-Radeon-R9-Nano-Fiji-GPU-Block-Diagram.jpg (315KB, 1366x768px) Image search: [Google]

315KB, 1366x768px

>>59693514

>>59693514
Its memory system is nothing like Fiji's though

File: furyx.png (515KB, 1228x1268px) Image search: [Google]

515KB, 1228x1268px

>>59692792
>>59692965
>>59693065
Fiji had some very suspect performance regarding its memory subsystem.

While Polaris doesn't look like it actively chokes in nearly the same way, it's clear that it's still bandwidth starved (mem OCs matter), indicating that better delta color compression, tiling rasterizers, etc. would have helped a lot.

>>59693582
Fiji was just unbalanced, high ALU and TMU throughput, catastrophic polyfill, either from lack of ROPs or something else(l2$?)

>>59693547
the memory subsystem is structurally identical and just varying in external bus and cache slice sizes.

the most commonly accepted theory is that GCN's central memory crossbar just doesn't scale past a certain point, which Fiji apparently hits.
the signs are that realizable HBM bandwidth is surprisingly low and that DCC yields really meager improvements:
>>59693582

https://videocardz.com/66359/amd-radeon-rx-500-series-to-launch-in-april

AYYMD HOUSEFIRES REBRANDEON can't even hit 1.5K, you think a much bigger AYYMD HOUSEFIRES can?

>>59693641
>>59693653
Fiji had several problems, most of which can be pretty easily identified here:
>>59693582

- really low Geometry Engine throughput (half that of the competition's): 1 tri/clock per each of 4 SEs
- low ROP ouput (2/3 that of 980 Ti). highly contentious how much this actually matters.
- unexpected poor bandwidth. allegedly the cause of "starved" shaders.
- 4x4px rasterizers vs. 2x4px for Nvidia: twice as much wasted capacity on small triangle, which is why HairWorks fucks over GCN comparatively more.

http://techreport.com/r.x/2017_03_08_Nvidia_s_GeForce_GTX_1080_Ti_graphics_card_reviewed/B3Dpixelfill.png

http://techreport.com/r.x/2017_03_08_Nvidia_s_GeForce_GTX_1080_Ti_graphics_card_reviewed/B3Dbandwidth.png

http://techreport.com/r.x/2017_03_08_Nvidia_s_GeForce_GTX_1080_Ti_graphics_card_reviewed/b3dtexturefill.png

http://techreport.com/r.x/2017_03_08_Nvidia_s_GeForce_GTX_1080_Ti_graphics_card_reviewed/B3Dpoly.png

AYYMD HOUSEFIRES, SUPER INEFFICIENT GARBAGE ARCHITECTURE

>>59693684
>>59693868
Are these the quality posts I heard about?

>>59693912
Something picked up on my filter so I can't tell you.

Le April Foolz!!! XD

>>59693937
>spamming the same links to """""review"""" sites
>typing in all caps
In my day shitposting was an art

>>59691679
If they have more TMUs, ROPs and not just optimized FuryX, then this will be dope.

>>59694141
I kinda miss the old days. Yes, even thermi shitposting.

>>59694160
I challenge you to name one title made in the last 3 years that's fill rate or texture sampling limited.

>>59694254
Skyrim

>>59694303
can't tell if b8 or retarded.