Every feature check ends the same way on both drivers.
Speed test scenes (benchmark)
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.
Scene
Stock ms
Custom ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
70.01 typical 69.96
69.81 typical 70.34
0% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
hdr_2160p
148.35 typical 148.11
148.49 typical 148.40
0% slower
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
oit_linked_lists
65.71 typical 66.77
59.15 typical 58.42
11% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers
56.80 typical 57.73
56.78 typical 57.52
0% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
subpasses
110.56 typical 111.10
110.67 typical 111.14
0% slower
3 of 3 vs 3 of 3
? 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-Mali-G57-2.0-rc1 against Mali-G52 MC2. "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-Mali-G57-2.0-rc1 (0)
None
Extensions only in Mali-G52 MC2 (0)
None
Core features that differ (0)
None
Limits that differ (0)
Limit
Stock
Custom
Formats supported by only one driver (0 gained, 0 lost)