Home / Adreno (TM) 22 / Compare

turnip_faux123_v1.1.7 vs turnip_mrpurple_T27-toasted

On Adreno (TM) 22 (HONOR 200 Pro, Moorechip Retroid Pocket G2, POCO F6, realme GT 6, realme 真我GT Neo6, Vivo iQOO Neo 10R, Xiaomi Pad 7 Pro, Xiaomi Pad 7 Pro). The first driver named is compared against the second, which is the baseline.

Stockturnip_mrpurple_T27-toastedPurpleVK 26.2.0-devel (git-e9f44bb883)

Customturnip_faux123_v1.1.7Mesa 26.3.0-devel (git-dd45fd0baa)

Graphics system version (Vulkan)? to ?

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

Features that pass their check (validated)not tested on bothturnip_mrpurple_T27-toasted and turnip_faux123_v1.1.7: no driver check yet

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

hdr_2160p2% faster
oit_linked_lists2% faster
pipeline_barriers_2160p2% faster
subpasses_2160p1% faster

Custom driver against stock, per scene. Bars to the right are faster, to the left slower.

Picture does not match the stock driver in 1 scene (oit_linked_lists). The custom driver drew something else there, so its frame time for that scene is not a fair number.

Small areas of the picture differ from the stock driver in 1 scene (pipeline_barriers: 1482 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).

turnip_mrpurple_T27-toasted details turnip_faux123_v1.1.7 details

Feature checks that differ

turnip_mrpurple_T27-toasted and turnip_faux123_v1.1.7: 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_mrpurple_T27-toasted ms	turnip_faux123_v1.1.7 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	8.74 typical 8.72	only one side	0 of 3 vs 3 of 3	? vs ? clock unknown	not checked
hdr_2160p	22.00 typical 21.90	21.65 typical 21.50	2% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.7 64x36
oit_linked_lists	20.62 typical 20.66	20.32 typical 20.34	2% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	differs 41.2 differs in 2124 small areas worst 207.0 64x36
pipeline_barriers	3.15 typical 2.97	3.09 typical 2.97	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 10.6 differs in 1482 small areas worst 62.3 64x36
pipeline_barriers_2160p	11.19 typical 10.41	10.99 typical 10.29	2% 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.52 typical 5.24	5.37 typical 5.19	too light, see subpasses_2160p	3 of 3 vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	20.05 typical 19.66	19.79 typical 19.56	1% 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 turnip_faux123_v1.1.7 against turnip_mrpurple_T27-toasted. "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.