Home / Adreno (TM) 740 / Compare

Turnip_v27.0.0-R1-Oneui vs Turnip_v26.3.0-R6

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_v26.3.0-R6Mesa 26.3.0-devel (git-a995eaeda4)

CustomTurnip_v27.0.0-R1-OneuiMesa 27.0.0-devel (git-f28352d117)

Graphics system version (Vulkan)1.4.363 to 1.4.363

Optional features (extensions)176 to 182+6 -0

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

Speed test scenes (benchmark)1 faster 2 slower 1 even14% faster 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_2160p118% faster
oit_linked_lists0% slower
pipeline_barriers_2160p15% slower
subpasses_2160p10% 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: 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).

Not on equal terms: the GPU clock differed during 1 of these scenes (for example subpasses_2160p: stock at 100% of the device's maximum, custom at 94%). Part of the frame-time difference comes from the clock the device chose, not from the driver.

Turnip_v26.3.0-R6 details Turnip_v27.0.0-R1-Oneui details

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

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	Turnip_v26.3.0-R6 ms	Turnip_v27.0.0-R1-Oneui ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	7.88 typical 8.01	only one side	0 of 3 vs 3 of 3	? vs 512 clock unknown	not checked
compute_nbody_2x	n/a	15.90 typical 15.86	only one side	? vs 3 of 3	? vs 719 clock unknown	not checked
hdr_2160p	35.53 typical 35.37	16.29 typical 16.20	118% faster	3 of 3 vs 3 of 3	680 vs 719	no large difference 0.0 no small difference worst 0.3 64x36
oit_linked_lists	26.67 typical 26.61	26.77 typical 26.86	0% slower	3 of 3 vs 3 of 3	680 vs 719	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	2.28 typical 2.26	2.31 typical 2.18	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	680 vs 719	no large difference 10.6 differs in 1482 small areas worst 62.3 64x36
pipeline_barriers_2160p	7.64 typical 7.66	9.02 typical 9.25	15% slower	3 of 3 vs 3 of 3	680 vs 719	no large difference 0.0 no small difference worst 0.0 64x36
subpasses	3.75 typical 3.74	3.59 typical 3.56	too light, see subpasses_2160p	3 of 3 vs 3 of 3	680 vs 719	not checked
subpasses_2160p	13.54 typical 13.51	14.98 typical 14.93	10% slower	3 of 3 vs 3 of 3	680 vs 678 not comparable	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_v27.0.0-R1-Oneui against Turnip_v26.3.0-R6. "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_v27.0.0-R1-Oneui (6)

VK_EXT_present_mode_fifo_latest_ready
VK_KHR_present_id
VK_KHR_present_id2
VK_KHR_present_wait2
VK_KHR_swapchain_maintenance1
VK_QCOM_rotated_copy_commands

Extensions only in Turnip_v26.3.0-R6 (0)

None

Core features that differ (0)

None

Limits that differ (0)

Limit	Turnip_v26.3.0-R6	Turnip_v27.0.0-R1-Oneui

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

Only in Turnip_v27.0.0-R1-Oneui:

None

Only in Turnip_v26.3.0-R6:

None