Home / Mali-G610 / Compare

EXP_PanVK-kbase-ace-lab86 vs panvk_faux123_ace_v0.36.0

On Mali-G610 (GameForce Ace, Infinix GT 20 Pro, Infinix NOTE Edge, Nothing Phone (2a) Plus, realme 真我 GT NEO 3 150W, Vivo V27, Xiaomi 13T). The first driver named is compared against the second, which is the baseline.

Stockpanvk_faux123_ace_v0.36.0PanVK-kbase beta.14 (Mesa 26.3.0-devel (git-5a07217f03))

CustomEXP_PanVK-kbase-ace-lab86PanVK-kbase RC3-lowmem (Mesa 26.3.0-devel (git-a6db27309d))

Graphics system version (Vulkan)1.4.363 to 1.4.363

Optional features (extensions)185 to 185+0 -0

Features that pass their check (validated)50 to 522 pass only on EXP_PanVK-kbase-ace-lab86 0 pass only on panvk_faux123_ace_v0.36.0

Speed test scenes (benchmark)3 faster 1 slower 1 even12% faster overall (geometric mean)

Games each driver could run (an estimate from its feature list): green likely, yellow maybe, orange limited, red no

StockDX92002+DX102006+DX112009+DX122015+Switch

CustomDX92002+DX102006+DX112009+DX122015+Switch

compute_nbody1% faster
hdr_2160p79% faster
oit_linked_lists16% slower
pipeline_barriers15% faster
subpasses3% faster

Custom driver against stock, per scene. Bars to the right are faster, to the left slower.

Small areas of the picture differ from the stock driver in 1 scene (pipeline_barriers: 1698 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

Not on equal terms: the GPU clock differed during 2 of these scenes (for example compute_nbody: stock at 88% of the device's maximum, custom at 100%). Part of the frame-time difference comes from the clock the device chose, not from the driver.

panvk_faux123_ace_v0.36.0 details EXP_PanVK-kbase-ace-lab86 details

Feature checks that differ (2)

Feature	panvk_faux123_ace_v0.36.0	EXP_PanVK-kbase-ace-lab86	Change
compat.helper_loop_terminator core	untested	pass	gained
compat.nested_map core	untested	pass	gained

Speed test scenes (benchmark)

Scene	panvk_faux123_ace_v0.36.0 ms	EXP_PanVK-kbase-ace-lab86 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	19.00 typical 18.85	18.89 typical 18.80	1% faster	3 of 3 vs 3 of 3	883 vs 1000 not comparable	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	57.63 typical 57.23	32.22 typical 31.79	79% faster	? vs 3 of 3	? vs 1000 clock unknown	not checked
oit_linked_lists	19.72 typical 19.70	23.40 typical 23.38	16% slower	3 of 3 vs 3 of 3	1000 vs 1000	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	10.20 typical 10.19	8.87 typical 8.87	15% faster	3 of 3 vs 3 of 3	1000 vs 1000	no large difference 8.5 differs in 1698 small areas worst 84.7 64x36
subpasses	19.31 typical 19.31	18.82 typical 18.83	3% faster	3 of 3 vs 3 of 3	900 vs 1000 not comparable	not checked

Time to draw one frame, per scene: the average (mean) frame time of the scene's best round, which is how many frames the driver delivered; lower is faster. "Typical" beside it is the median frame, which can sit well under the average when a driver's frames come in two speeds. A pair of reports made before per-round averages were recorded is compared on the median. A scene whose rounds disagree by more than 15% is left out. A scene marked "paced" was held at that mean frame time by the driver or the display queue, together with at least one other scene of the same run; its time says how the frames were spaced, not how fast the driver rendered, so it is not compared. A scene marked "too light" took under 8 ms at the standard size (1920 by 1080) on both drivers, where the screen's frame queue spaces the frames more than the chip does; its heavier run is the one compared: the row ending in _2160p is the scene drawn at 3840 by 2160, and compute_nbody_2x is that scene with twice the particles. "Faster" and "slower" describe EXP_PanVK-kbase-ace-lab86 against panvk_faux123_ace_v0.36.0. "Picture vs stock" compares one fixed frame per scene as a coarse colour grid (0 is identical, above 40 is a different picture); it finds a scene that was not drawn. Where both reports carry the finer 64x36 grid, the second figure is how many of its 2,304 cells differ by more than 4 of 255, and "worst" is the largest single cell; this is what finds a small rendering error in a picture that otherwise matches. A row marked 16x9 comes from a report made before the finer grid existed. "Starts" is how many of a scene's process starts reached a measured round. A GPU clock marked "not comparable" differed by more than 5% of the device's maximum between the two timings.

Technical differences (Vulkan)

Extensions only in EXP_PanVK-kbase-ace-lab86 (0)

None

Extensions only in panvk_faux123_ace_v0.36.0 (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	panvk_faux123_ace_v0.36.0	EXP_PanVK-kbase-ace-lab86

Formats supported by only one driver (0 gained, 0 lost)

Only in EXP_PanVK-kbase-ace-lab86:

None

Only in panvk_faux123_ace_v0.36.0:

None