Home / Adreno (TM) 740 / Compare

turnip_faux123_v1.2.3 vs turnip_faux123_v1.2.2

On Adreno (TM) 740 (AYN Odin2, AYN Odin2 Portal, AYN Thor, HONOR Magic5 Pro, Moorechip Retroid Pocket 6, Moorechip Retroid Pocket Nova, motorola edge plus 2023, OnePlus 11 5G, OnePlus 12R, POCO F6 Pro, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23 Ultra, Samsung Galaxy S23 Ultra, Samsung Galaxy S23+, Samsung Galaxy Z Fold5, Sony Xperia 1 V, Xiaomi 13 pro). The first driver named is compared against the second, which is the baseline.

Stockturnip_faux123_v1.2.2Mesa 26.3.0-devel (git-dd45fd0baa)

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

Graphics system version (Vulkan)1.4.359 to 1.4.359

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

Features that pass their check (validated)70 to 70turnip_faux123_v1.2.2 and turnip_faux123_v1.2.3: sent from a device this site could not confirm (unverified)both pass the same checks

Speed test scenes (benchmark)0 faster 1 slower 3 even3% 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_2160p11% slower
oit_linked_lists1% faster
pipeline_barriers_2160p2% slower
subpasses0% faster

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

turnip_faux123_v1.2.2 details turnip_faux123_v1.2.3 details

Feature checks that differ (0)

Unverified turnip_faux123_v1.2.2 and turnip_faux123_v1.2.3: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

Every feature check ends the same way on both drivers.

Speed test scenes (benchmark)

unverified turnip_faux123_v1.2.2 and turnip_faux123_v1.2.3: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

Scene	turnip_faux123_v1.2.2 ms	turnip_faux123_v1.2.3 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	n/a	only one side	3 of 3 vs 3 of 3	488 vs 488	no large difference 0.0 no small difference worst 0.0 64x36
compute_nbody_2x	16.16	n/a	only one side	3 of 3 vs 3 of 3	719 vs 669	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	13.78 typical 12.83	15.52 typical 14.95	11% slower	3 of 3 vs 3 of 3	565 vs 528	no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists	25.03 typical 25.10	24.84 typical 24.90	1% faster	3 of 3 vs 3 of 3	719 vs 719	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	2.16 typical 2.15	2.17 typical 2.15	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	719 vs 719	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers_2160p	7.83 typical 7.70	7.96 typical 7.68	2% slower	3 of 3 vs 3 of 3	719 vs 693	no large difference 0.0 no small difference worst 0.0 64x36
subpasses	3.44 typical 3.43	3.44 typical 3.43	0% faster	3 of 3 vs 3 of 3	719 vs 719	not checked
subpasses_2160p	12.39	n/a	only one side	3 of 3 vs 3 of 3	719 vs 719	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.2.3 against turnip_faux123_v1.2.2. "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 turnip_faux123_v1.2.3 (0)

None

Extensions only in turnip_faux123_v1.2.2 (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	turnip_faux123_v1.2.2	turnip_faux123_v1.2.3

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

Only in turnip_faux123_v1.2.3:

None

Only in turnip_faux123_v1.2.2:

None