Home / Adreno (TM) 825 / Compare

stable-turnip-sync-V2 vs mainline-turnip-sync-V32

On Adreno (TM) 825 (Nothing Phone (3), Poco F7, Poco F7). The first driver named is compared against the second, which is the baseline.

Stockmainline-turnip-sync-V32Mesa 26.3.0-devel (git-9c7e022677)

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

Graphics system version (Vulkan)1.4.363 to 1.4.354

Optional features (extensions)178 to 174+0 -4

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

Speed test scenes (benchmark)0 faster 1 slower 1 even2% slower 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_2160p0% 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 1 scene (pipeline_barriers: 1181 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

mainline-turnip-sync-V32 details stable-turnip-sync-V2 details

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

Speed test scenes (benchmark)

Scene	mainline-turnip-sync-V32 ms	stable-turnip-sync-V2 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	18.07	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	26.15 typical 26.03	26.14 typical 26.03	0% 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	n/a	22.92	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	n/a	11.04	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 6.2 differs in 1181 small areas worst 46.0 64x36
subpasses	n/a	n/a	too light, see subpasses_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	19.82 typical 19.83	20.46 typical 20.43	3% slower	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 stable-turnip-sync-V2 against mainline-turnip-sync-V32. "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 stable-turnip-sync-V2 (0)

None

Extensions only in mainline-turnip-sync-V32 (4)

VK_EXT_image_compression_control
VK_EXT_shader_subgroup_vote
VK_KHR_shader_quad_control
VK_VALVE_buffer_device_address_allocation_alignment

Core features that differ (0)

None

Limits that differ (1)

Limit	mainline-turnip-sync-V32	stable-turnip-sync-V2
maxComputeWorkGroupInvocations	2048	1024

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

Only in stable-turnip-sync-V2:

None

Only in mainline-turnip-sync-V32:

None