|
|
|
|
|
by vardump
3979 days ago
|
|
As a software dev who has used and benefited from AVX2, I think the last data point in the chart is quite a bit off. Perhaps their benchmarking software didn't support AVX2 yet (Haswell/Broadwell) yet? > Blue depicts parallel performance, while purely sequential performance is shown in orange. Sequential trend seems to totally disregard up to doubled integer vector performance in AVX2, first introduced in Haswell. Original AVX didn't support 256-bit wide integer vectors. Also Haswell up to "doubled" [1] FLOP/cycle. [1]: If your workload is FMA. That said, it is a pretty common FPU workload. See for example http://stackoverflow.com/questions/15655835/flops-per-cycle-... for reference. |
|
The reason the CPU bottlenecked pre-DX12/pre-Vulkan games is because a hefty amount of it was used for the abstraction: likely little of which was FLOPs. Basically: you forgot to profile first ;). For a purely graphics workload the CPU will be doing relatively small amounts of work.
In addition I can say with fair certainty that a smaller portion of the gamer market upgrades their CPU on a regular basis (so-called enthusiasts). Taking myself as an example: I haven't upgraded my CPU since 2010 and I've only started feeling that pinch this year. That's a lot of CPUs without AVX2 support.
TLDR; AVX2 is currently in the "solutions looking for a problem" bucket.