Turnip_v26.3.0-R5 vs adreno-driver-842.8
On Adreno (TM) 750 (OnePlus 13R, OnePlus 13R, Redmi K70 Pro, Samsung Galaxy S24, Samsung Galaxy S24 Ultra, Samsung Galaxy S24 Ultra, Samsung Galaxy Z Flip6, Samsung Galaxy Z Fold6, Samsung Galaxy Z Fold6, ZTE REDMAGIC 9). The first driver named is compared against the second, which is the baseline.
Stockadreno-driver-842.8Driver Build: f6b5df5188, I29aebc4401, 1758283784
vsCustomTurnip_v26.3.0-R5
Graphics system version (Vulkan)? to ?
Optional features (extensions)? to ?not checked on both
Features that pass their check (validated)not tested on bothadreno-driver-842.8 and Turnip_v26.3.0-R5: no driver check yet
Speed test scenes (benchmark)1 faster 1 slower0% faster overall (geometric mean)
- hdr_2160p22% slower
- pipeline_barriers30% faster
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 2 scenes (pipeline_barriers: 1896 of 2304 cells, pipeline_barriers_2160p: 1414 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).
Not on equal terms: the GPU clock differed during 2 of these scenes (for example hdr_2160p: stock at 100% of the device's maximum, custom at 95%). Part of the frame-time difference comes from the clock the device chose, not from the driver.
adreno-driver-842.8 details Turnip_v26.3.0-R5 details
Feature checks that differ
adreno-driver-842.8 and Turnip_v26.3.0-R5: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
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 | adreno-driver-842.8 ms | Turnip_v26.3.0-R5 ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 8.38 typical 8.64 | n/a | only one side | 3 of 3 vs 0 of 3 | 641 vs ? clock unknown | not checked |
| hdr_2160p | 15.54 typical 15.39 | 19.99 typical 20.04 | 22% slower | 3 of 3 vs 3 of 3 | 903 vs 857 not comparable | no large difference 0.0 no small difference worst 0.0 64x36 |
| oit_linked_lists | 18.65 | n/a | only one side | 3 of 3 vs 3 of 3 | 1000 vs 1000 | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | 2.77 typical 2.33 | 2.14 typical 1.90 | 30% faster | 3 of 3 vs 3 of 3 | 655 vs 834 not comparable | no large difference 11.0 differs in 1896 small areas worst 46.3 64x36 |
| pipeline_barriers_2160p | 6.36 | n/a | only one side | 3 of 3 vs 3 of 3 | 903 vs 903 | no large difference 9.1 differs in 1414 small areas worst 68.0 64x36 |
| subpasses | n/a | n/a | only one side | 3 of 3 vs 3 of 3 | 840 vs 903 not comparable | not checked |
| subpasses_2160p | 10.09 | n/a | only one side | 3 of 3 vs 3 of 3 | 935 vs 919 | 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 Turnip_v26.3.0-R5 against adreno-driver-842.8. "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.