a8xx-gen8-V22 vs Turnip_Gen8_V38
On Adreno (TM) 840 (HONOR Magic8 pro, iQOO 15, LENOVO TB324ZC, nubia NX809J, OnePlus 15, POCO F8 Ultra, POCO F9 Ultra, realme RMX5210, Samsung Galaxy S26, Samsung Galaxy S26, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy Z Fold8, Samsung Galaxy Z Fold8 Ultra, Xiaomi 17, Xiaomi 2512BPNDAG). The first driver named is compared against the second, which is the baseline.
StockTurnip_Gen8_V38Mesa 27.0.0-devel (git-f28352d117)
vsCustoma8xx-gen8-V22Mesa 26.1.0-devel (git-cb20f767c9)
Graphics system version (Vulkan)1.4.363 to ?
Optional features (extensions)185 to ?not checked on both
Features that pass their check (validated)not tested on botha8xx-gen8-V22: no driver check yet
Speed test scenes (benchmark)3 faster 0 slower9% faster overall (geometric mean)
- hdr_2160p17% faster
- oit_linked_lists5% faster
- pipeline_barriers4% faster
Custom driver against stock, per scene. Bars to the right are faster, to the left slower.
Picture does not match the stock driver in 1 scene (hdr_2160p). The custom driver drew something else there, so its frame time for that scene is not a fair number.
Small areas of the picture differ from the stock driver in 3 scenes (oit_linked_lists: 1610 of 2304 cells, pipeline_barriers: 2295 of 2304 cells, pipeline_barriers_2160p: 2300 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.
Did not start every time: compute_nbody (stock 3 of 3, custom 0 of 3).
Turnip_Gen8_V38 details a8xx-gen8-V22 details
Feature checks that differ
a8xx-gen8-V22: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
Speed test scenes (benchmark)
| Scene | Turnip_Gen8_V38 ms | a8xx-gen8-V22 ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | n/a | n/a | only one side | 3 of 3 vs 0 of 3 | ? vs ? clock unknown | not checked |
| compute_nbody_2x | 10.55 typical 10.64 | n/a | only one side | 3 of 3 vs ? | ? vs ? clock unknown | not checked |
| hdr_2160p | 8.91 typical 9.15 | 7.59 typical 7.09 | 17% faster | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | differs 82.3 differs in 2304 small areas worst 189.7 64x36 |
| oit_linked_lists | 12.89 typical 12.61 | 12.24 typical 12.26 | 5% faster | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 17.7 differs in 1610 small areas worst 173.7 64x36 |
| pipeline_barriers | 1.56 typical 1.46 | 1.50 typical 1.42 | 4% faster | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 36.1 differs in 2295 small areas worst 129.0 64x36 |
| pipeline_barriers_2160p | 6.27 | n/a | only one side | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | no large difference 33.4 differs in 2300 small areas worst 115.0 64x36 |
| subpasses | n/a | 2.09 | only one side | 3 of 3 vs 3 of 3 | ? vs ? clock unknown | not checked |
| subpasses_2160p | n/a | n/a | only one side | 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 a8xx-gen8-V22 against Turnip_Gen8_V38. "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.