Zink OpenGL-Over-Vulkan At ~97% Piglit Testing Conformance

[R41N3R]

Some benchmarks would be interesting at this point :-) Just to see how well it works already now on ANV & RADV compared to the classic OpenGL drivers.

[_ONH_]

If the 4.5 or something in that ballpark is upstream, beforehand it seems to me to take to much effort which changes altogether to fast I think.

[smitty3268]

Little or no effort has gone into the performance of Zink at this time, so comparing it and especially using it as the basis for unrelated comparisons is silly.

I don't think that's entirely true. Mike Blumenkrantz spent a while optimizing things over the last month, and made really good progress. He also said that he reached the limit of what is easily achievable for now, which is why he switched back over to fixing bugs. There will certainly be more performance changes to come, but it's at the point where I think performance comparisons are useful and unlikely to massively change day to day anymore.

[oiaohm]

Something to consider is if you put zink head to head with llvmpipe or any of the other software options its insanely fast. 50 percent of Intel at first does not sound that good.

Lets say you have a program that for some reason is glitching with the native opengl driver. Current options is drop to llvmpipe and in most cases be lucky to get 5 frames per second.

If Zink ends up faster that is good. But Zink at it current speed for the cases where drivers don't work right its a hell of a improvement.

[nanonyme]

The Zink code in Mesa is at OpenGL 3.3, so when will the new updated Zink code with support for OpenGL 4+ be merged into mainline Mesa?

With it being 69% the speed of Intel's OpenGL driver, is there any room for improvement? What can we expect? What can we hope for?

Also another interesting point is how comparable Zink with DSA will be to regular GL driver with DSA. There might be less overhead emulating OpenGL at that point.