Originally posted by LinAGKar
View Post
Announcement
Collapse
No announcement yet.
LLVMpipe Now Exposes OpenGL 4.2 For GL On CPUs
Collapse
X
-
Originally posted by starshipeleven View PostSince for GPUs the "muh singlethred puhfomance" argument never applied, even when CPUs hit a brick wall and Moore's Law died (somewhere in the Sandy/Ivybridge era) GPUs have kept increasing their performance each generation at more or less the same speed.
Comment
-
Originally posted by pal666 View Posti didn't check it, but i expect llvmpipe to be multithreaded just like gpus
CPU performance stopped jumping by 40-60% each gen and started going more towards the 15% in optimistic slides, while GPUs just added MOAR CORES as they always did (plus the usual architectural development) and kept increasing their power by the same pace.
As exemplified by most gaming rigs, A LOT of people is still fine with Sandy/Ivy and slightly newer CPUs, but you still need to change GPU every 2 years at most if you want to stay on top of the graphics game.
And this should translate in the fact that GPUs performance would increase MUCH faster than CPU-running-LLVMpipe performance.
Comment
-
I'd love to see Linux Tech Tips (pun intended) do benchmarks on LLVM Pipe software rendering vs swiftshader and even more "gotta go fast" with gentoo buildtime optimizations.Last edited by commodore256; 06 July 2020, 07:01 PM.
Comment
-
Said it before and will say it again: what llvmpipe exposes is not my concern. The real issue here is performance.
I was setting up two Windows 10 installations a couple of weeks ago, one on a Skylake laptop with the standard Intel iGPU, the other on an Athlon 3000G with enbedded Vega graphics. Even without the GPU drivers, the Windows 10 GUI was able to fun at full speed with all those transparency and fade effects.
On the other hand, Gnome 3 and Plasma Wayland were practically unusable on my dual-Xeon monster with 48 processor cores under llvmpipe.
As for the fellow who gave "Just disable compositing" as a solution, go and actually use Plasma Wayland before commenting further.
There really needs to be some form of performant CPU-backed compositing in Wayland compositors as a last resort, especially for computers that use Nvidia hardware with the Nouveau driver. QSG_RENDER_LOOP=basic is no guarantee that a Plasma Wayland session won't lock up under Nouveau, while Gnome doesn't even have the option to disable threaded GL rendering.
Last edited by Sonadow; 07 July 2020, 05:30 AM.
Comment
-
Originally posted by starshipeleven View PostCPU performance stopped jumping by 40-60% each gen and started going more towards the 15% in optimistic slides, while GPUs just added MOAR CORES as they always did (plus the usual architectural development) and kept increasing their power by the same pace.
Originally posted by starshipeleven View PostAs exemplified by most gaming rigs, A LOT of people is still fine with Sandy/Ivy and slightly newer CPUs, but you still need to change GPU every 2 years at most if you want to stay on top of the graphics game.
Originally posted by starshipeleven View PostAnd this should translate in the fact that GPUs performance would increase MUCH faster than CPU-running-LLVMpipe performance.
Comment
-
Originally posted by pal666 View Postthere's no difference between cpu and gpu progress with comparable workloads
because those people run single-threaded workloads. with multithreaded workloads new cpu is just as important as new gpu
You can add all cores you want in a CPU, only workstation users will notice past the 8 cores mark.
you are wrong
Comment
-
Comment