Home / Adreno (TM) 610 / Compare

Turnip_v26.3.0-R5 vs adreno690

On Adreno (TM) 610 (HONOR Pad X8a, HONOR X8c, POCO M7, Redmi Note 11, Redmi Note 12, Redmi Note 13, Samsung Galaxy A05s, Xiaomi 220333QAG). The first driver named is compared against the second, which is the baseline.

Stockadreno690Driver Build: 99ab7c9669, I88f9ec120a, 1670935924

CustomTurnip_v26.3.0-R5

Graphics system version (Vulkan)? to ?

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

Features that pass their check (validated)not tested on bothadreno690 and Turnip_v26.3.0-R5: no driver check yet

Speed test scenes (benchmark)1 faster 2 slower12% slower overall (geometric mean)

oit_linked_lists16% faster
pipeline_barriers17% slower
subpasses30% 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: 1333 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), hdr_2160p (stock 0 of 3, custom 3 of 3).

adreno690 details Turnip_v26.3.0-R5 details

Feature checks that differ

adreno690 and Turnip_v26.3.0-R5: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

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	adreno690 ms	Turnip_v26.3.0-R5 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	87.10 typical 86.82	n/a	only one side	3 of 3 vs 0 of 3	? vs ? clock unknown	not checked
hdr_2160p	n/a	353.21 typical 351.25	only one side	0 of 3 vs 3 of 3	? vs 1025 clock unknown	not checked
oit_linked_lists	114.00 typical 113.62	98.70 typical 97.42	16% faster	3 of 3 vs 3 of 3	? vs 1025 clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	37.93 typical 38.20	45.46 typical 45.24	17% slower	3 of 3 vs 3 of 3	? vs 1025 clock unknown	no large difference 7.0 differs in 1333 small areas worst 47.7 64x36
subpasses	61.99 typical 62.02	89.05 typical 89.04	30% slower	3 of 3 vs 3 of 3	? vs 1025 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_v26.3.0-R5 against adreno690. "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.