Home / Mali-G610 / Compare

panvk_faux123_v1.0.1 vs EXP_PanVK-kbase-ace-lab86

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.

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

Custompanvk_faux123_v1.0.1PanVK-kbase RC3-lowmem (Mesa 26.3.0-devel (git-f9ed07a075))

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)52 to 6513 pass only on panvk_faux123_v1.0.1 0 pass only on EXP_PanVK-kbase-ace-lab86

Speed test scenes (benchmark)no shared scenes

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

EXP_PanVK-kbase-ace-lab86 details panvk_faux123_v1.0.1 details

Feature checks that differ (13)

Feature	EXP_PanVK-kbase-ace-lab86	panvk_faux123_v1.0.1	Change
depthClamp VkPhysicalDeviceFeatures	untested	pass	gained
largePoints VkPhysicalDeviceFeatures	untested	pass	gained
core.blend_advertised_formats core	untested	pass	gained
core.compute_big_stack core	untested	pass	gained
core.host_coherent_readback core	untested	pass	gained
core.mrt_partial_kill core	untested	pass	gained
core.ubo_update_buffer core	untested	pass	gained
core.ubo_written_after_record core	untested	pass	gained
core.varying_subset core	untested	pass	gained
mem.image_padding core	untested	pass	gained
stage.geometry_max_output core	untested	pass	gained
stage.geometry_point_size core	untested	pass	gained
sync.first_submit_clear_then_compute core	untested	pass	gained

Speed test scenes (benchmark)

Scene	EXP_PanVK-kbase-ace-lab86 ms	panvk_faux123_v1.0.1 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	18.89 typical 18.80	n/a	only one side	3 of 3 vs ?	1000 vs ? clock unknown	not checked
hdr_2160p	32.22 typical 31.79	n/a	only one side	3 of 3 vs ?	1000 vs ? clock unknown	not checked
oit_linked_lists	23.40 typical 23.38	n/a	only one side	3 of 3 vs ?	1000 vs ? clock unknown	not checked
pipeline_barriers	8.87 typical 8.87	n/a	only one side	3 of 3 vs ?	1000 vs ? clock unknown	not checked
subpasses	18.82 typical 18.83	n/a	only one side	3 of 3 vs ?	1000 vs ? clock unknown	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 panvk_faux123_v1.0.1 against EXP_PanVK-kbase-ace-lab86. "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 panvk_faux123_v1.0.1 (0)

None

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

None

Core features that differ (0)

None

Limits that differ (0)

Limit	EXP_PanVK-kbase-ace-lab86	panvk_faux123_v1.0.1

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

Only in panvk_faux123_v1.0.1:

None

Only in EXP_PanVK-kbase-ace-lab86:

None