mesa-turnip-main-V26.1-eden-fix-latest-crash-fix vs Turnip_MTR_v1.5_A8XX
On Adreno (TM) 830 (AYN Odin 3). The first driver named is compared against the second, which is the baseline.
StockTurnip_MTR_v1.5_A8XXMesa 26.1.0-devel-lto (git-efb5ab1e4b)
vsCustommesa-turnip-main-V26.1-eden-fix-latest-crash-fixMesa 26.1.0-devel (git-402bd37f9d)
Graphics system version (Vulkan)? to ?
Optional features (extensions)? to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip_MTR_v1.5_A8XX and mesa-turnip-main-V26.1-eden-fix-latest-crash-fix: no driver check yet
Speed test scenes (benchmark)0 faster 4 slower14% slower overall (geometric mean)
- hdr_2160p11% slower
- oit_linked_lists6% slower
- pipeline_barriers_2160p18% slower
- subpasses_2160p19% 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: 1632 of 2304 cells, pipeline_barriers_2160p: 311 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 0 of 3, custom 3 of 3).
Not on equal terms: the GPU clock differed during 2 of these scenes (for example pipeline_barriers_2160p: stock at 99% of the device's maximum, custom at 81%). Part of the frame-time difference comes from the clock the device chose, not from the driver.
Turnip_MTR_v1.5_A8XX details mesa-turnip-main-V26.1-eden-fix-latest-crash-fix details
Feature checks that differ
Turnip_MTR_v1.5_A8XX and mesa-turnip-main-V26.1-eden-fix-latest-crash-fix: 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_MTR_v1.5_A8XX ms | mesa-turnip-main-V26.1-eden-fix-latest-crash-fix ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | n/a | 5.47 typical 5.37 | only one side | 0 of 3 vs 3 of 3 | ? vs 880 clock unknown | not checked |
| compute_nbody_2x | n/a | n/a | only one side | ? vs 3 of 3 | ? vs 1100 clock unknown | not checked |
| hdr_2160p | 14.89 typical 14.96 | 16.72 typical 16.53 | 11% slower | 3 of 3 vs 3 of 3 | 1100 vs 1100 | no large difference 0.0 no small difference worst 0.7 64x36 |
| oit_linked_lists | 17.26 typical 17.27 | 18.39 typical 18.34 | 6% slower | 3 of 3 vs 3 of 3 | 1100 vs 1100 | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | 1.97 typical 1.90 | 4.62 typical 4.73 | too light, see pipeline_barriers_2160p | 3 of 3 vs 3 of 3 | 1100 vs 660 not comparable | no large difference 10.7 differs in 1632 small areas worst 83.7 64x36 |
| pipeline_barriers_2160p | 7.33 typical 6.86 | 8.91 typical 8.79 | 18% slower | 3 of 3 vs 3 of 3 | 1092 vs 891 not comparable | no large difference 0.9 differs in 311 small areas worst 47.3 64x36 |
| subpasses | 3.12 typical 3.01 | 6.90 typical 7.05 | too light, see subpasses_2160p | 3 of 3 vs 3 of 3 | 1100 vs 986 not comparable | not checked |
| subpasses_2160p | 11.58 typical 11.16 | 14.30 typical 14.50 | 19% slower | 3 of 3 vs 3 of 3 | 1100 vs 922 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 mesa-turnip-main-V26.1-eden-fix-latest-crash-fix against Turnip_MTR_v1.5_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.