According to the commit, they enabled loop unrolling? Im not that experienced with reading this stuff, but if I had to guess, I'd say that'd be what did it
Phoronix is going to be flooded with almost identical headlines like this if they make an article every time the (brand-new) NVK Mesa driver gets a commit that improves performance somewhere
9 Comments
pelya@lemmy.world · 28 pts · 2y
With such a headline, I'm going to believe they have removed
usleep(10000)from the frame rendering code.GustavoM@lemmy.world · 6 pts · 2y
Nah, they reduced its
If { else ifsequences.shadoh@lemmy.world · 7 pts · 2y
According to the commit, they enabled loop unrolling? Im not that experienced with reading this stuff, but if I had to guess, I'd say that'd be what did it
sugar_in_your_tea@sh.itjust.works · 6 pts · 2y
Yup, that's the one line change, enabling loop unrolling.
ichbinjasokreativ@lemmy.world · 1 pts · 2y
loop-unrolling.enable()
LiveLM@lemmy.zip · 5 pts · 2y
Honestly, the Talos Principle Vulkan implementation feels so broken/underbaked I'm surprised anyone's testing new drivers with it
Narann@lemmy.world · 4 pts · 2y
Yes, bad use of API shouldn’t be use as reference, but it also increases Valheim (which does not seems to be the best API us ever):
Commit here.
They simply added this line
op.max_unroll_iterations = 32;, related to NIR shader compilation. Passed to NIR here.(I stop here, lost track and interest in further investigation)
noodlejetski@lemm.ee · 2 pts · 2y
now let's see whether the next patch bumps it to 27 or 36 fps!
merthyr1831@lemmy.world · 2 pts · 2y
Phoronix is going to be flooded with almost identical headlines like this if they make an article every time the (brand-new) NVK Mesa driver gets a commit that improves performance somewhere