Turnip_v26.0.0_R1 vs Qualcomm Technologies Inc. Adreno Vulkan Driver
On Adreno (TM) 740 (AYN Odin2, AYN Odin2 Portal, AYN Thor, Moorechip Retroid Pocket Nova, motorola edge plus 2023, OnePlus 11 5G, POCO F6 Pro, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23 Ultra, Samsung Galaxy S23 Ultra, Samsung Galaxy S23+, Sony Xperia 1 V, Xiaomi 13 pro). The first driver named is compared against the second, which is the baseline.
StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 3df4c357f0, I515341007c, 1769513954
vsCustomTurnip_v26.0.0_R1Mesa 26.0.0-devel (git-cc1d942727)
Graphics system version (Vulkan)1.3.128 to ?
Optional features (extensions)115 to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip_v26.0.0_R1: no driver check yet
Speed test scenes (benchmark)1 faster 2 slower3% slower overall (geometric mean)
- hdr_2160p12% slower
- pipeline_barriers_2160p7% faster
- subpasses_2160p3% 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 2 scenes (pipeline_barriers: 1694 of 2304 cells, pipeline_barriers_2160p: 1037 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 pipeline_barriers_2160p: stock at 90% of the device's maximum, custom at 100%). Part of the frame-time difference comes from the clock the device chose, not from the driver.
Qualcomm Technologies Inc. Adreno Vulkan Driver details Turnip_v26.0.0_R1 details
Feature checks that differ
Turnip_v26.0.0_R1: 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 | Stock ms | Custom ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 7.84 typical 7.85 | n/a | only one side | 3 of 3 vs 0 of 3 | 561 vs ? clock unknown | not checked |
| compute_nbody_2x | 25.49 typical 25.89 | n/a | only one side | 3 of 3 vs ? | 550 vs ? clock unknown | not checked |
| hdr_2160p | 26.73 typical 25.77 | 30.28 typical 29.42 | 12% slower | 3 of 3 vs 3 of 3 | 550 vs 615 | no large difference 0.0 no small difference worst 0.3 64x36 |
| oit_linked_lists | n/a | 29.28 | only one side | 3 of 3 vs 3 of 3 | 719 vs 615 | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | n/a | 2.55 | too light, see pipeline_barriers_2160p | 3 of 3 vs 3 of 3 | 680 vs 615 | no large difference 9.3 differs in 1694 small areas worst 47.3 64x36 |
| pipeline_barriers_2160p | 9.55 typical 9.22 | 8.91 typical 8.82 | 7% faster | 3 of 3 vs 3 of 3 | 495 vs 615 not comparable | no large difference 6.4 differs in 1037 small areas worst 51.7 64x36 |
| subpasses | 5.53 typical 4.57 | 4.30 typical 4.24 | too light, see subpasses_2160p | 3 of 3 vs 3 of 3 | 549 vs 615 not comparable | not checked |
| subpasses_2160p | 15.58 typical 15.40 | 16.00 typical 15.92 | 3% slower | 3 of 3 vs 3 of 3 | 550 vs 570 not comparable | 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.0.0_R1 against Qualcomm Technologies Inc. Adreno Vulkan Driver. "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.