FauxVkDB
English
Home / Mali-G710 MC7 / Compare

EXP_PanVK-kbase-pixel7-lab86 vs EXP_panvk_pixel7_lab11tls

On Mali-G710 MC7 (Google Pixel 7, Google Pixel 7a). The first driver named is compared against the second, which is the baseline.

StockEXP_panvk_pixel7_lab11tlsPanVK-kbase RC3 (Mesa 26.3.0-devel (git-5a07217f03))
vs
CustomEXP_PanVK-kbase-pixel7-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)186 to 186+0 -0
Features that pass their check (validated)50 to 52EXP_panvk_pixel7_lab11tls and EXP_PanVK-kbase-pixel7-lab86: sent from a device this site could not confirm (unverified)2 pass only on EXP_PanVK-kbase-pixel7-lab86 0 pass only on EXP_panvk_pixel7_lab11tls
Speed test scenes (benchmark)2 faster 1 slower 1 even1% 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_nbody4% slower
  • oit_linked_lists1% slower
  • pipeline_barriers_2160p3% faster
  • subpasses6% faster

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

Did not start every time: hdr_2160p (stock 2 of 3, custom 3 of 3).

EXP_panvk_pixel7_lab11tls details EXP_PanVK-kbase-pixel7-lab86 details

Feature checks that differ (2)

Unverified EXP_panvk_pixel7_lab11tls and EXP_PanVK-kbase-pixel7-lab86: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

FeatureEXP_panvk_pixel7_lab11tlsEXP_PanVK-kbase-pixel7-lab86Change
compat.helper_loop_terminator
core
untestedpassgained
compat.nested_map
core
untestedpassgained

Speed test scenes (benchmark)

unverified EXP_PanVK-kbase-pixel7-lab86: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

The two drivers were not measured on the same set of device models. Frame times from different devices do not compare drivers, so read these numbers with that in mind.

SceneEXP_panvk_pixel7_lab11tls msEXP_PanVK-kbase-pixel7-lab86 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody14.90 typical 14.8015.56 typical 15.434% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
hdr_2160pn/a21.54only one side2 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists19.89 typical 19.6920.14 typical 20.041% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers6.69 typical 6.686.15 typical 6.13too light, see pipeline_barriers_2160p3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers_2160p20.56 typical 20.5219.94 typical 19.933% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
subpasses13.26 typical 13.2512.55 typical 12.556% faster3 of 3 vs 3 of 3? vs ? clock unknownnot 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-pixel7-lab86 against EXP_panvk_pixel7_lab11tls. "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-pixel7-lab86 (0)
  • None
Extensions only in EXP_panvk_pixel7_lab11tls (0)
  • None
Core features that differ (0)
None
Limits that differ (0)
LimitEXP_panvk_pixel7_lab11tlsEXP_PanVK-kbase-pixel7-lab86
Formats supported by only one driver (0 gained, 0 lost)

Only in EXP_PanVK-kbase-pixel7-lab86:

  • None

Only in EXP_panvk_pixel7_lab11tls:

  • None