WN-Turnip-1.19-b_Axxx vs mesa-turnip-main-V26.1-eden-fix-latest-crash-fix

On Adreno (TM) 830 (AYN Odin 3). The first driver named is compared against the second, which is the baseline.

Stockmesa-turnip-main-V26.1-eden-fix-latest-crash-fixMesa 26.1.0-devel (git-402bd37f9d)

CustomWN-Turnip-1.19-b_AxxxMesa 26.3.0-devel (git-30da39187d)

Graphics system version (Vulkan)? to ?

Optional features (extensions)? to ?not checked on both

Features that pass their check (validated)not tested on bothmesa-turnip-main-V26.1-eden-fix-latest-crash-fix and WN-Turnip-1.19-b_Axxx: no driver check yet

Speed test scenes (benchmark)4 faster 0 slower45% faster overall (geometric mean)

hdr_2160p30% faster
oit_linked_lists5% faster
pipeline_barriers_2160p83% faster
subpasses_2160p75% 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 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 2 of these scenes (for example pipeline_barriers_2160p: stock at 81% of the device's maximum, custom at 98%). Part of the frame-time difference comes from the clock the device chose, not from the driver.

mesa-turnip-main-V26.1-eden-fix-latest-crash-fix details WN-Turnip-1.19-b_Axxx details

Feature checks that differ

mesa-turnip-main-V26.1-eden-fix-latest-crash-fix and WN-Turnip-1.19-b_Axxx: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

Scene	mesa-turnip-main-V26.1-eden-fix-latest-crash-fix ms	WN-Turnip-1.19-b_Axxx ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	5.47 typical 5.37	n/a	only one side	3 of 3 vs 0 of 3	880 vs ? clock unknown	not checked
compute_nbody_2x	n/a	n/a	only one side	3 of 3 vs ?	1100 vs ? clock unknown	not checked
hdr_2160p	16.72 typical 16.53	12.88 typical 12.83	30% faster	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	18.39 typical 18.34	17.44 typical 17.43	5% faster	3 of 3 vs 3 of 3	1100 vs 1100	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	4.62 typical 4.73	2.77 typical 2.15	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	660 vs 660	no large difference 10.6 differs in 1486 small areas worst 62.7 64x36
pipeline_barriers_2160p	8.91 typical 8.79	4.86 typical 4.85	83% faster	3 of 3 vs 3 of 3	891 vs 1075 not comparable	no large difference 0.0 no small difference worst 0.0 64x36
subpasses	6.90 typical 7.05	3.07 typical 2.71	too light, see subpasses_2160p	3 of 3 vs 3 of 3	986 vs 964	not checked
subpasses_2160p	14.30 typical 14.50	8.19 typical 8.18	75% faster	3 of 3 vs 3 of 3	922 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 WN-Turnip-1.19-b_Axxx against mesa-turnip-main-V26.1-eden-fix-latest-crash-fix. "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.