adreno690 vs turnip_mrpurple_T30-toasted
On Adreno (TM) 610 (HONOR Pad X8a, HONOR X8c, POCO M7, Redmi Note 12, Redmi Note 13, Xiaomi 220333QAG). The first driver named is compared against the second, which is the baseline.
Stockturnip_mrpurple_T30-toastedPurpleVK 26.3.0-devel (git-62ac221a33)
vsCustomadreno690Driver Build: 99ab7c9669, I88f9ec120a, 1670935924
Graphics system version (Vulkan)? to ?
Optional features (extensions)? to ?not checked on both
Features that pass their check (validated)not tested on bothturnip_mrpurple_T30-toasted and adreno690: no driver check yet
Speed test scenes (benchmark)no shared scenes
turnip_mrpurple_T30-toasted details adreno690 details
Feature checks that differ
turnip_mrpurple_T30-toasted and adreno690: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
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.
| Scene | turnip_mrpurple_T30-toasted ms | adreno690 ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | n/a | 87.10 typical 86.82 | only one side | 0 of 3 vs 3 of 3 | ? vs ? clock unknown | not checked |
| oit_linked_lists | n/a | 114.00 typical 113.62 | only one side | 0 of 3 vs 3 of 3 | ? vs ? clock unknown | not checked |
| pipeline_barriers | n/a | 37.93 typical 38.20 | only one side | 0 of 3 vs 3 of 3 | ? vs ? clock unknown | not checked |
| subpasses | n/a | 61.99 typical 62.02 | only one side | 0 of 3 vs 3 of 3 | ? vs ? clock unknown | not 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 adreno690 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)
Both drivers need a driver check (validation report) before their technical details (Vulkan) can be compared.