FauxVkDB
English
Home / Adreno (TM) 825 / Compare

stable-turnip-sync-V2 vs vturnip_mrpurple_T30-toasted.adpkg_turnip_mrpurple_T30-toasted

On Adreno (TM) 825 (Nothing Phone (3), OnePlus Nord 6, Poco F7, Poco F7, REDMI Turbo 4 Pro). The first driver named is compared against the second, which is the baseline.

Stockvturnip_mrpurple_T30-toasted.adpkg_turnip_mrpurple_T30-toastedPurpleVK 26.3.0-devel (git-62ac221a33)
vs
Customstable-turnip-sync-V2Mesa 26.2.3 (git-fbc44a3bcc)
Graphics system version (Vulkan)? to 1.4.354
Optional features (extensions)? to 174not checked on both
Features that pass their check (validated)not tested on bothvturnip_mrpurple_T30-toasted.adpkg_turnip_mrpurple_T30-toasted: no driver check yet
Speed test scenes (benchmark)1 faster 1 slower 1 even31% slower overall (geometric mean)
  • hdr_2160p1% slower
  • pipeline_barriers75% slower
  • subpasses_2160p37% 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: 1552 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).

vturnip_mrpurple_T30-toasted.adpkg_turnip_mrpurple_T30-toasted details stable-turnip-sync-V2 details

Feature checks that differ

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

Speed test scenes (benchmark)

Scenevturnip_mrpurple_T30-toasted.adpkg_turnip_mrpurple_T30-toasted msstable-turnip-sync-V2 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/a18.10 typical 18.07only one side0 of 3 vs 3 of 3? vs ? clock unknownnot checked
hdr_2160p25.89 typical 25.2126.14 typical 26.031% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
oit_linked_listsn/a22.92only one side3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers2.70 typical 2.5210.96 typical 11.0475% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 8.2 differs in 1552 small areas worst 53.7 64x36
pipeline_barriers_2160p9.87 typical 9.97n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
subpassesn/an/atoo light, see subpasses_2160p3 of 3 vs 3 of 3? vs ? clock unknownnot checked
subpasses_2160p27.97 typical 27.7220.46 typical 20.4337% faster3 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 stable-turnip-sync-V2 against vturnip_mrpurple_T30-toasted.adpkg_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)

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