FauxVkDB
English
Home / Adreno (TM) 740 / Compare

turnip_mrpurple_T30-toasted vs turnip_faux123_v1.1.7

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_faux123_v1.1.7Mesa 26.3.0-devel (git-dd45fd0baa)
vs
Customturnip_mrpurple_T30-toastedPurpleVK 26.3.0-devel (git-62ac221a33)
Graphics system version (Vulkan)1.4.359 to 1.4.359
Optional features (extensions)172 to 168+0 -4
Features that pass their check (validated)50 to 490 pass only on turnip_mrpurple_T30-toasted 1 pass only on turnip_faux123_v1.1.7
Speed test scenes (benchmark)0 faster 3 slower 1 even7% 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_2160p5% slower
  • oit_linked_lists0% faster
  • pipeline_barriers_2160p9% slower
  • subpasses_2160p13% 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 2 scenes (pipeline_barriers: 1702 of 2304 cells, pipeline_barriers_2160p: 1596 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 3 of 3, custom 0 of 3).

turnip_faux123_v1.1.7 details turnip_mrpurple_T30-toasted details

Feature checks that differ (1)

Featureturnip_faux123_v1.1.7turnip_mrpurple_T30-toastedChange
core.copy_wide_row_length
core
passfaillost

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_faux123_v1.1.7 msturnip_mrpurple_T30-toasted msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody5.68 typical 5.63n/aonly one side3 of 3 vs 0 of 3680 vs ? clock unknownnot checked
compute_nbody_2x17.77 typical 17.72n/aonly one side3 of 3 vs ?680 vs ? clock unknownnot checked
hdr_2160p35.11 typical 35.0436.96 typical 36.905% slower3 of 3 vs 3 of 3680 vs 680 no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists26.54 typical 26.4526.49 typical 26.420% faster3 of 3 vs 3 of 3680 vs 719 no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers2.28 typical 2.282.40 typical 2.28too light, see pipeline_barriers_2160p3 of 3 vs 3 of 3680 vs 719 no large difference 11.2 differs in 1702 small areas worst 62.0 64x36
pipeline_barriers_2160p7.63 typical 7.628.35 typical 8.389% slower3 of 3 vs 3 of 3680 vs 706 no large difference 9.1 differs in 1596 small areas worst 69.7 64x36
subpasses3.80 typical 3.803.99 typical 3.99too light, see subpasses_2160p3 of 3 vs 3 of 3680 vs 719 not checked
subpasses_2160p13.70 typical 13.7115.79 typical 15.9913% slower3 of 3 vs 3 of 3646 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_mrpurple_T30-toasted against turnip_faux123_v1.1.7. "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_mrpurple_T30-toasted (0)
  • None
Extensions only in turnip_faux123_v1.1.7 (4)
  • VK_EXT_shader_subgroup_vote
  • VK_KHR_compute_shader_derivatives
  • VK_KHR_maintenance7
  • VK_KHR_shader_relaxed_extended_instruction
Core features that differ (0)
None
Limits that differ (2)
Limitturnip_faux123_v1.1.7turnip_mrpurple_T30-toasted
maxComputeSharedMemorySize3276865536
timestampPeriod52.083333.1126
Formats supported by only one driver (0 gained, 0 lost)

Only in turnip_mrpurple_T30-toasted:

  • None

Only in turnip_faux123_v1.1.7:

  • None