FauxVkDB
English
Home / Adreno (TM) 830 / Compare

Turnip_Gen8_V37 vs Qualcomm Technologies Inc. Adreno Vulkan Driver

On Adreno (TM) 830 (AYN Odin 3). The first driver named is compared against the second, which is the baseline.

StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 3967b80d3b, Ica4ce9bea6, 1770914544
vs
CustomTurnip_Gen8_V37Mesa 26.3.0-devel (git-a995eaeda4)
Graphics system version (Vulkan)1.3.284 to ?
Optional features (extensions)164 to ?not checked on both
Features that pass their check (validated)not tested on bothTurnip_Gen8_V37: no driver check yet
Speed test scenes (benchmark)0 faster 4 slower 1 even9% slower overall (geometric mean)
  • compute_nbody_2x21% slower
  • hdr_2160p11% slower
  • oit_linked_lists6% slower
  • pipeline_barriers_2160p0% slower
  • subpasses_2160p4% 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: 1337 of 2304 cells, pipeline_barriers_2160p: 1038 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

Not on equal terms: the GPU clock differed during 4 of these scenes (for example compute_nbody_2x: 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.

Not compared: 3 scenes with a paced frame rate (compute_nbody, pipeline_barriers, subpasses). At least one of the two drivers was held at a fixed frame rate there, so the two times do not measure the same thing.

Qualcomm Technologies Inc. Adreno Vulkan Driver details Turnip_Gen8_V37 details

Feature checks that differ

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

Speed test scenes (benchmark)

SceneStock msCustom msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodypaced at 4.113.37 typical 3.28too light, see compute_nbody_2x3 of 3 vs 3 of 3967 vs 1100 not comparableno large difference 0.0 no small difference worst 0.0 64x36
compute_nbody_2x8.49 typical 8.4210.71 typical 10.6621% slower3 of 3 vs 3 of 3967 vs 1100 not comparableno large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p13.63 typical 13.5215.34 typical 15.3211% slower? vs 3 of 3? vs 1092 clock unknownnot checked
oit_linked_lists16.38 typical 16.3217.44 typical 17.446% slower3 of 3 vs 3 of 3967 vs 1100 not comparableno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barrierspaced at 2.731.57 typical 1.43too light, see pipeline_barriers_2160p3 of 3 vs 3 of 3967 vs 1100 not comparableno large difference 7.1 differs in 1337 small areas worst 48.0 64x36
pipeline_barriers_2160p6.02 typical 6.156.04 typical 6.350% slower3 of 3 vs 3 of 3967 vs 1100 not comparableno large difference 6.4 differs in 1038 small areas worst 51.7 64x36
subpassespaced at 2.742.52 typical 2.32too light, see subpasses_2160p3 of 3 vs 3 of 3967 vs 1100 not comparablenot checked
subpasses_2160p9.44 typical 9.409.80 typical 9.824% slower3 of 3 vs 3 of 3967 vs 1100 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_Gen8_V37 against Qualcomm Technologies Inc. Adreno Vulkan Driver. "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.