FauxVkDB
English
Home / Adreno (TM) 740 / Compare

turnip_faux123_v1.1.7 vs turnip_mrpurple_T26-toasted

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

Stockturnip_mrpurple_T26-toastedPurpleVK 26.1.0-devel (git-1c4d081f8c)
vs
Customturnip_faux123_v1.1.7Mesa 26.3.0-devel (git-dd45fd0baa)
Graphics system version (Vulkan)1.4.344 to 1.4.359
Optional features (extensions)166 to 172+6 -0
Features that pass their check (validated)49 to 501 pass only on turnip_faux123_v1.1.7 0 pass only on turnip_mrpurple_T26-toasted
Speed test scenes (benchmark)1 faster 2 slower 1 even8% 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_2160p28% slower
  • oit_linked_lists4% slower
  • pipeline_barriers_2160p0% slower
  • subpasses_2160p4% 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: 1329 of 2304 cells, pipeline_barriers_2160p: 1187 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_T26-toasted details turnip_faux123_v1.1.7 details

Feature checks that differ (1)

Featureturnip_mrpurple_T26-toastedturnip_faux123_v1.1.7Change
core.copy_wide_row_length
core
failpassgained

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.

Sceneturnip_mrpurple_T26-toasted msturnip_faux123_v1.1.7 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/a5.68 typical 5.63only one side0 of 3 vs 3 of 3? vs 680 clock unknownnot checked
compute_nbody_2xn/a17.77 typical 17.72only one side? vs 3 of 3? vs 680 clock unknownnot checked
hdr_2160p25.33 typical 25.2635.11 typical 35.0428% slower3 of 3 vs 3 of 3680 vs 680 no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists25.38 typical 25.3026.54 typical 26.454% slower3 of 3 vs 3 of 3680 vs 680 no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers3.26 typical 2.782.28 typical 2.28too light, see pipeline_barriers_2160p3 of 3 vs 3 of 3572 vs 680 not comparableno large difference 7.1 differs in 1329 small areas worst 68.3 64x36
pipeline_barriers_2160p7.62 typical 7.637.63 typical 7.620% slower3 of 3 vs 3 of 3680 vs 680 no large difference 7.5 differs in 1187 small areas worst 86.0 64x36
subpasses4.46 typical 4.413.80 typical 3.80too light, see subpasses_2160p3 of 3 vs 3 of 3680 vs 680 not checked
subpasses_2160p14.30 typical 14.3013.70 typical 13.714% faster3 of 3 vs 3 of 3680 vs 646 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.1.7 against turnip_mrpurple_T26-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)

Extensions only in turnip_faux123_v1.1.7 (6)
  • VK_EXT_debug_marker
  • VK_EXT_depth_clamp_control
  • VK_EXT_image_compression_control
  • VK_EXT_primitive_restart_index
  • VK_EXT_shader_image_atomic_int64
  • VK_EXT_shader_subgroup_vote
Extensions only in turnip_mrpurple_T26-toasted (0)
  • None
Core features that differ (1)
multiviewGeometryShader Vulkan 1.1unsupported to pass
Limits that differ (2)
Limitturnip_mrpurple_T26-toastedturnip_faux123_v1.1.7
maxFragmentInputComponents124128
timestampPeriod33.112652.0833
Formats supported by only one driver (2 gained, 0 lost)

Only in turnip_faux123_v1.1.7:

  • R64_SINT
  • R64_UINT

Only in turnip_mrpurple_T26-toasted:

  • None