Home / Adreno (TM) 650 / Compare

Qualcomm_819.2_adpkg vs turnip_mrpurple_T30-toasted

On Adreno (TM) 650 (blackshark SHARK PAR-A0, MANGMI Pocket Max, Moorechip Retroid Pocket 5, POCO F4, Samsung Galaxy S20 FE, Samsung Galaxy S20 FE 5G, Sony Xperia 5 II). The first driver named is compared against the second, which is the baseline.

Stockturnip_mrpurple_T30-toastedPurpleVK 26.3.0-devel (git-62ac221a33)

CustomQualcomm_819.2_adpkgDriver Build: 651341e91d, I8d46b3bbb7, 1754290135

Graphics system version (Vulkan)? to ?

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

Features that pass their check (validated)not tested on bothturnip_mrpurple_T30-toasted and Qualcomm_819.2_adpkg: no driver check yet

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

hdr_2160p22% faster
oit_linked_lists2% faster
pipeline_barriers_2160p14% faster
subpasses19% 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 2 scenes (pipeline_barriers: 1855 of 2304 cells, pipeline_barriers_2160p: 1737 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_T30-toasted details Qualcomm_819.2_adpkg details

Feature checks that differ

turnip_mrpurple_T30-toasted and Qualcomm_819.2_adpkg: 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_T30-toasted ms	Qualcomm_819.2_adpkg ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	11.36 typical 11.33	only one side	0 of 3 vs 3 of 3	? vs 670 clock unknown	not checked
hdr_2160p	97.15 typical 96.71	79.51 typical 79.39	22% faster	3 of 3 vs 3 of 3	670 vs 670	no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists	34.15 typical 34.12	33.34 typical 33.35	2% faster	3 of 3 vs 3 of 3	670 vs 670	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	4.99 typical 4.78	4.89 typical 4.74	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	670 vs 670	no large difference 13.2 differs in 1855 small areas worst 64.7 64x36
pipeline_barriers_2160p	19.57 typical 20.03	17.11 typical 17.46	14% faster	3 of 3 vs 3 of 3	656 vs 670	no large difference 11.5 differs in 1737 small areas worst 57.7 64x36
subpasses	9.31 typical 9.58	7.83 typical 7.65	19% faster	3 of 3 vs 3 of 3	670 vs 670	not checked
subpasses_2160p	n/a	29.07 typical 29.07	only one side	? vs 3 of 3	? vs 670 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 Qualcomm_819.2_adpkg against turnip_mrpurple_T30-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.