Home / Adreno (TM) 660 / Compare

turnip_faux123_v1.2.0 vs turnip_faux123_v1.1.9-rc14

On Adreno (TM) 660 (Asus ROG Phone 5 series, Razer Edge, Samsung Galaxy S21 Ultra 5G, Samsung Galaxy S21+ 5G, Sony Xperia PRO-I). The first driver named is compared against the second, which is the baseline.

Stockturnip_faux123_v1.1.9-rc14Mesa 26.3.0-devel (git-dd45fd0baa)

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

Graphics system version (Vulkan)1.3.359 to 1.3.359

Optional features (extensions)164 to 163+0 -1

Features that pass their check (validated)50 to 6515 pass only on turnip_faux123_v1.2.0 0 pass only on turnip_faux123_v1.1.9-rc14

Speed test scenes (benchmark)3 faster 0 slower 2 even19% 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

compute_nbody9% faster
hdr_2160p102% faster
oit_linked_lists3% faster
pipeline_barriers_2160p1% faster
subpasses_2160p2% 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: 1358 of 2304 cells, pipeline_barriers_2160p: 1342 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

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

turnip_faux123_v1.1.9-rc14 details turnip_faux123_v1.2.0 details

Feature checks that differ (15)

Feature	turnip_faux123_v1.1.9-rc14	turnip_faux123_v1.2.0	Change
depthClamp VkPhysicalDeviceFeatures	untested	pass	gained
largePoints VkPhysicalDeviceFeatures	untested	pass	gained
compat.helper_loop_terminator core	untested	pass	gained
compat.nested_map core	untested	pass	gained
core.blend_advertised_formats core	untested	pass	gained
core.compute_big_stack core	untested	pass	gained
core.host_coherent_readback core	untested	pass	gained
core.mrt_partial_kill core	untested	pass	gained
core.ubo_update_buffer core	untested	pass	gained
core.ubo_written_after_record core	untested	pass	gained
core.varying_subset core	untested	pass	gained
mem.image_padding core	untested	pass	gained
stage.geometry_max_output core	untested	pass	gained
stage.geometry_point_size core	untested	pass	gained
sync.first_submit_clear_then_compute core	untested	pass	gained

Speed test scenes (benchmark)

Scene	turnip_faux123_v1.1.9-rc14 ms	turnip_faux123_v1.2.0 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	12.65 typical 12.93	11.59 typical 11.75	9% faster	3 of 3 vs 3 of 3	697 vs 642 not comparable	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	69.31 typical 67.58	34.35 typical 34.40	102% faster	3 of 3 vs 3 of 3	809 vs 840	no large difference 0.0 no small difference worst 0.3 64x36
oit_linked_lists	30.88 typical 30.96	29.95 typical 30.00	3% faster	3 of 3 vs 3 of 3	840 vs 752 not comparable	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	3.78 typical 3.78	3.74 typical 3.68	too light, see pipeline_barriers_2160p	3 of 3 vs 3 of 3	792 vs 830	no large difference 9.3 differs in 1358 small areas worst 79.0 64x36
pipeline_barriers_2160p	14.42 typical 14.34	14.23 typical 14.36	1% faster	3 of 3 vs 3 of 3	745 vs 762	no large difference 9.1 differs in 1342 small areas worst 73.3 64x36
subpasses	6.18 typical 6.08	6.11 typical 6.06	too light, see subpasses_2160p	3 of 3 vs 3 of 3	819 vs 830	not checked
subpasses_2160p	23.48 typical 23.62	23.08 typical 23.28	2% faster	3 of 3 vs 3 of 3	775 vs 792	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.0 against turnip_faux123_v1.1.9-rc14. "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.0 (0)

None

Extensions only in turnip_faux123_v1.1.9-rc14 (1)

VK_EXT_image_compression_control

Core features that differ (0)

None

Limits that differ (0)

Limit	turnip_faux123_v1.1.9-rc14	turnip_faux123_v1.2.0

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

Only in turnip_faux123_v1.2.0:

None

Only in turnip_faux123_v1.1.9-rc14:

None