FauxVkDB
English
Home / Adreno (TM) 610 / Compare

Turnip_v26.3.0-R5 vs Turnip_v27.0.0-R1

On Adreno (TM) 610 (HONOR Pad X8a, HONOR X8c, POCO M7, Redmi Note 11, Redmi Note 12, Redmi Note 13, Samsung Galaxy A05s, Xiaomi 220333QAG). The first driver named is compared against the second, which is the baseline.

StockTurnip_v27.0.0-R1Mesa 27.0.0-devel (git-f28352d117)
vs
CustomTurnip_v26.3.0-R5
Graphics system version (Vulkan)1.3.363 to ?
Optional features (extensions)158 to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip_v26.3.0-R5: no driver check yet
Speed test scenes (benchmark)0 faster 0 slower 4 even1% slower overall (geometric mean)
  • hdr_2160p2% slower
  • oit_linked_lists1% slower
  • pipeline_barriers1% slower
  • subpasses0% 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 3 of 3, custom 0 of 3).

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

Turnip_v27.0.0-R1 details Turnip_v26.3.0-R5 details

Feature checks that differ

Turnip_v26.3.0-R5: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

SceneTurnip_v27.0.0-R1 msTurnip_v26.3.0-R5 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody89.38 typical 89.17n/aonly one side3 of 3 vs 0 of 31115 vs ? clock unknownnot checked
hdr_2160p347.46 typical 347.29353.21 typical 351.252% slower3 of 3 vs 3 of 31115 vs 1025 no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists98.08 typical 96.1898.70 typical 97.421% slower3 of 3 vs 3 of 31115 vs 1025 no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers45.04 typical 45.3545.46 typical 45.241% slower3 of 3 vs 3 of 31115 vs 1025 no large difference 10.6 differs in 1482 small areas worst 62.3 64x36
subpasses88.72 typical 88.7389.05 typical 89.040% slower3 of 3 vs 3 of 3982 vs 1025 not comparablenot 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_v26.3.0-R5 against Turnip_v27.0.0-R1. "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)

Both drivers need a driver check (validation report) before their technical details (Vulkan) can be compared.