Turnip-Rutabaga-v3 vs Turnip-v26.3.0-20261010-A8xx
On Adreno (TM) 830 (HONOR AAK-AN00, HONOR Magic V5, nubia NX789J, OnePlus 13, POCO F8 Pro, realme GT 7 Pro, Samsung Galaxy S25, Samsung Galaxy S25 Ultra, Samsung Galaxy S25 Ultra, Samsung Galaxy S25 Ultra, Samsung Galaxy S25+, Xiaomi 15, ZTE NP05J). The first driver named is compared against the second, which is the baseline.
StockTurnip-v26.3.0-20261010-A8xxMesa 26.3.0-devel (git-bffd91947e)
vsCustomTurnip-Rutabaga-v3Mesa 26.3.0-devel (git-b00479181d)
Graphics system version (Vulkan)? to ?
Optional features (extensions)? to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip-v26.3.0-20261010-A8xx and Turnip-Rutabaga-v3: no driver check yet
Speed test scenes (benchmark)3 faster 1 slower1% slower overall (geometric mean)
- hdr_2160p2% faster
- oit_linked_lists5% faster
- pipeline_barriers_2160p7% faster
- subpasses_2160p17% 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: 1486 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 4 of these scenes (for example hdr_2160p: stock at 82% 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.
Turnip-v26.3.0-20261010-A8xx details Turnip-Rutabaga-v3 details
Feature checks that differ
Turnip-v26.3.0-20261010-A8xx and Turnip-Rutabaga-v3: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
Speed test scenes (benchmark)
unverified Turnip-Rutabaga-v3: The times below were sent from a device this site could not confirm. A result the site counts replaces them.
| Scene | Turnip-v26.3.0-20261010-A8xx ms | Turnip-Rutabaga-v3 ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 10.38 typical 10.14 | n/a | only one side | 3 of 3 vs 0 of 3 | 373 vs ? clock unknown | not checked |
| hdr_2160p | 16.60 typical 16.39 | 16.20 typical 16.19 | 2% faster | 3 of 3 vs 3 of 3 | 900 vs 1100 not comparable | no large difference 0.0 no small difference worst 0.0 64x36 |
| oit_linked_lists | 21.28 typical 20.92 | 20.35 typical 20.35 | 5% faster | 3 of 3 vs 3 of 3 | 900 vs 1100 not comparable | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | 1.70 typical 1.67 | 1.63 typical 1.62 | too light, see pipeline_barriers_2160p | 3 of 3 vs 3 of 3 | 900 vs 1100 not comparable | no large difference 10.6 differs in 1486 small areas worst 62.7 64x36 |
| pipeline_barriers_2160p | 6.14 typical 6.00 | 5.75 typical 5.74 | 7% faster | 3 of 3 vs 3 of 3 | 787 vs 1027 not comparable | no large difference 0.0 no small difference worst 0.0 64x36 |
| subpasses | 2.78 typical 2.77 | 3.25 typical 3.25 | too light, see subpasses_2160p | 3 of 3 vs 3 of 3 | 900 vs 1100 not comparable | not checked |
| subpasses_2160p | 10.37 typical 10.37 | 12.54 typical 12.53 | 17% slower | 3 of 3 vs 3 of 3 | 900 vs 1100 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-Rutabaga-v3 against Turnip-v26.3.0-20261010-A8xx. "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.