FauxVkDB
English
Home / Adreno (TM) 640 / Compare

Turnip_v26.3.0-R5 vs Turnip_v26.3.0-R6

On Adreno (TM) 640 (Samsung Galaxy Note10+, Samsung Galaxy S10+, Samsung Galaxy S10+, Xiaomi Pad 5). The first driver named is compared against the second, which is the baseline.

StockTurnip_v26.3.0-R6Mesa 26.3.0-devel (git-a995eaeda4)
vs
CustomTurnip_v26.3.0-R5
Graphics system version (Vulkan)1.3.363 to 1.3.359
Optional features (extensions)158 to 157+0 -1
Features that pass their check (validated)48 to 48Turnip_v26.3.0-R6 and Turnip_v26.3.0-R5: sent from a device this site could not confirm (unverified)both pass the same checks
Speed test scenes (benchmark)0 faster 0 slower 4 even0% 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_2160p1% faster
  • oit_linked_lists1% faster
  • pipeline_barriers0% faster
  • subpasses1% slower

Custom driver against stock, per scene. Bars to the right are faster, to the left slower.

Turnip_v26.3.0-R6 details Turnip_v26.3.0-R5 details

Feature checks that differ (0)

Unverified Turnip_v26.3.0-R6 and Turnip_v26.3.0-R5: The results below were sent from a device this site could not confirm. A result the site counts replaces them.

Every feature check ends the same way on both drivers.

Speed test scenes (benchmark)

unverified Turnip_v26.3.0-R6 and Turnip_v26.3.0-R5: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

SceneTurnip_v26.3.0-R6 msTurnip_v26.3.0-R5 msDifferenceStartsGPU clock, MHzPicture vs stock
hdr_2160p121.24 typical 118.09120.46 typical 117.581% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists41.16 typical 40.8040.94 typical 40.751% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers8.05 typical 7.888.05 typical 7.930% faster3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
subpasses12.27 typical 12.4012.37 typical 12.531% slower3 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_v26.3.0-R5 against Turnip_v26.3.0-R6. "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_v26.3.0-R5 (0)
  • None
Extensions only in Turnip_v26.3.0-R6 (1)
  • VK_VALVE_buffer_device_address_allocation_alignment
Core features that differ (0)
None
Limits that differ (0)
LimitTurnip_v26.3.0-R6Turnip_v26.3.0-R5
Formats supported by only one driver (0 gained, 0 lost)

Only in Turnip_v26.3.0-R5:

  • None

Only in Turnip_v26.3.0-R6:

  • None