FauxVkDB
English
Home / Adreno (TM) 840 / Compare

Turnip_Gen8_V38 vs turnip_mrpurple_T30-toasted

On Adreno (TM) 840 (HONOR Magic8 pro, iQOO 15, LENOVO TB324ZC, nubia NX809J, OnePlus 15, POCO F8 Ultra, POCO F9 Ultra, realme RMX5210, Samsung Galaxy S26, Samsung Galaxy S26, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy S26 Ultra, Samsung Galaxy Z Fold8, Samsung Galaxy Z Fold8 Ultra, Xiaomi 17, Xiaomi 2512BPNDAG). The first driver named is compared against the second, which is the baseline.

Stockturnip_mrpurple_T30-toastedPurpleVK 26.3.0-devel (git-62ac221a33)
vs
CustomTurnip_Gen8_V38Mesa 27.0.0-devel (git-f28352d117)
Graphics system version (Vulkan)1.4.359 to 1.4.363
Optional features (extensions)178 to 185+7 -0
Features that pass their check (validated)61 to 654 pass only on Turnip_Gen8_V38 0 pass only on turnip_mrpurple_T30-toasted
Speed test scenes (benchmark)2 faster 1 slower26% 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_2160p6% slower
  • oit_linked_lists33% faster
  • pipeline_barriers59% 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 1 scene (pipeline_barriers: 1486 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_T30-toasted details Turnip_Gen8_V38 details

Feature checks that differ (4)

Featureturnip_mrpurple_T30-toastedTurnip_Gen8_V38Change
depthClamp
VkPhysicalDeviceFeatures
untestedpassgained
largePoints
VkPhysicalDeviceFeatures
untestedpassgained
perf.fb_local_barrier_large_draws
core
untestedpassgained
perf.fb_local_barrier_overdraw
core
untestedpassgained

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_T30-toasted msTurnip_Gen8_V38 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/an/aonly one side0 of 3 vs 3 of 3? vs ? clock unknownnot checked
compute_nbody_2xn/a10.55 typical 10.64only one side? vs 3 of 3? vs ? clock unknownnot checked
hdr_2160p8.42 typical 8.488.91 typical 9.156% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists17.09 typical 16.9812.89 typical 12.6133% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers2.48 typical 2.261.56 typical 1.4659% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 10.6 differs in 1486 small areas worst 62.7 64x36
pipeline_barriers_2160pn/a6.27only one side3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
subpasses5.21n/aonly one side3 of 3 vs 3 of 3? vs ? clock unknownnot checked
subpasses_2160p13.21n/aonly one side3 of 3 vs 3 of 3? vs ? clock unknownnot 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_Gen8_V38 against turnip_mrpurple_T30-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_Gen8_V38 (7)
  • VK_EXT_shader_subgroup_vote
  • VK_KHR_compute_shader_derivatives
  • VK_KHR_maintenance7
  • VK_KHR_shader_quad_control
  • VK_KHR_shader_relaxed_extended_instruction
  • VK_QCOM_rotated_copy_commands
  • VK_VALVE_buffer_device_address_allocation_alignment
Extensions only in turnip_mrpurple_T30-toasted (0)
  • None
Core features that differ (0)
None
Limits that differ (1)
Limitturnip_mrpurple_T30-toastedTurnip_Gen8_V38
timestampPeriod33.112652.0833
Formats supported by only one driver (0 gained, 0 lost)

Only in Turnip_Gen8_V38:

  • None

Only in turnip_mrpurple_T30-toasted:

  • None