Home / Adreno (TM) 825 / Compare

WN-Turnip-1.19-p_Axxx vs stable-turnip-sync-V2

On Adreno (TM) 825 (Nothing Phone (3), OnePlus Nord 6, Oppo K13 Turbo Pro 5G, Poco F7, Poco F7, REDMI Turbo 4 Pro). The first driver named is compared against the second, which is the baseline.

Stockstable-turnip-sync-V2Mesa 26.2.3 (git-fbc44a3bcc)

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

Graphics system version (Vulkan)1.4.354 to 1.4.363

Optional features (extensions)174 to 179+5 -0

Features that pass their check (validated)49 to 49both pass the same checks

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

Games each driver could run (an estimate from its feature list): green likely, yellow maybe, orange limited, red no

StockDX92002+DX102006+DX112009+DX122015+Switch

CustomDX92002+DX102006+DX112009+DX122015+Switch

hdr_2160p179% faster
oit_linked_lists35% faster
pipeline_barriers_2160p18% faster
subpasses_2160p32% 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).

stable-turnip-sync-V2 details WN-Turnip-1.19-p_Axxx details

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

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	stable-turnip-sync-V2 ms	WN-Turnip-1.19-p_Axxx ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	18.10 typical 18.07	n/a	only one side	3 of 3 vs 0 of 3	? vs ? clock unknown	not checked
hdr_2160p	26.14 typical 26.03	9.37 typical 9.11	179% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists	23.38 typical 22.92	17.36 typical 17.11	35% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	10.96 typical 11.04	2.78 typical 2.01	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 10.6 differs in 1486 small areas worst 62.7 64x36
pipeline_barriers_2160p	10.01 typical 9.86	8.50 typical 8.46	18% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
subpasses	5.19	n/a	too light, see subpasses_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	20.46 typical 20.43	15.50 typical 15.73	32% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	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-p_Axxx against stable-turnip-sync-V2. "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)

Extensions only in WN-Turnip-1.19-p_Axxx (5)

VK_EXT_image_compression_control
VK_EXT_shader_subgroup_ballot
VK_EXT_shader_subgroup_vote
VK_KHR_shader_quad_control
VK_VALVE_buffer_device_address_allocation_alignment

Extensions only in stable-turnip-sync-V2 (0)

None

Core features that differ (0)

None

Limits that differ (1)

Limit	stable-turnip-sync-V2	WN-Turnip-1.19-p_Axxx
maxComputeSharedMemorySize	65536	32768

Formats supported by only one driver (0 gained, 0 lost)

Only in WN-Turnip-1.19-p_Axxx:

None

Only in stable-turnip-sync-V2:

None