panvk-exynos9611-winlator-v0.02 vs Mali-G52
On Mali-G52 (CHUWI HiPad-Air, HONOR X5c, HONOR X5c, Infinix HOT 60i, Oppo A18, Oppo A38, realme RMX3710, Redmi 12, Redmi 12C, Redmi 14C, Redmi 15C, TECNO POVA 3, TECNO SPARK 20, Xiaomi 24049RN28L). The first driver named is compared against the second, which is the baseline.
StockMali-G52v1.r27p0-01eac0.560a3910a3367e0bb739a6eb4e910d0f
vsCustompanvk-exynos9611-winlator-v0.02Mesa 27.0.0-devel (git-18275303ac)
Graphics system version (Vulkan)1.1.149 to ?
Optional features (extensions)58 to ?not checked on both
Features that pass their check (validated)not tested on bothpanvk-exynos9611-winlator-v0.02: no driver check yet
Speed test scenes (benchmark)0 faster 4 slower 1 even14% slower overall (geometric mean)
- compute_nbody14% slower
- hdr_2160p0% faster
- oit_linked_lists18% slower
- pipeline_barriers24% slower
- subpasses10% slower
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: 1831 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.
Mali-G52 details panvk-exynos9611-winlator-v0.02 details
Feature checks that differ
panvk-exynos9611-winlator-v0.02: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
Speed test scenes (benchmark)
unverified Mali-G52 and panvk-exynos9611-winlator-v0.02: The times below were sent from a device this site could not confirm. A result the site counts replaces them.
| Scene | Stock ms | Custom ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 64.02 typical 63.06 | 74.13 typical 73.47 | 14% slower | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 0.1 no small difference worst 3.7 64x36 |
| hdr_2160p | 161.37 typical 159.01 | 160.86 typical 157.15 | 0% faster | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 0.0 no small difference worst 0.0 64x36 |
| oit_linked_lists | 71.56 typical 71.03 | 87.44 typical 85.26 | 18% slower | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | 44.75 typical 3.42 | 58.73 typical 52.51 | 24% slower | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 11.6 differs in 1831 small areas worst 85.3 64x36 |
| subpasses | 99.31 typical 3.84 | 110.86 typical 103.92 | 10% 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-exynos9611-winlator-v0.02 against Mali-G52. "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)
Both drivers need a driver check (validation report) before their technical details (Vulkan) can be compared.