Balemuni_Apex_v2_ULTIMATE_SD8Gen2 vs vulkan-805-adpkg
On Adreno (TM) 22 (HONOR 200 Pro, Moorechip Retroid Pocket G2, POCO F6, realme GT 6, realme 真我GT Neo6, Vivo iQOO Neo 10R, Xiaomi Pad 7 Pro, Xiaomi Pad 7 Pro). The first driver named is compared against the second, which is the baseline.
Stockvulkan-805-adpkgDriver Build: d4f1d5539c, Iad64dfeba7, 1731002436
vsCustomBalemuni_Apex_v2_ULTIMATE_SD8Gen2Mesa 26.3.0-devel (SD 8 Gen 2 / Adreno 740 Apex v2 Ultimate by Balemuni)
Graphics system version (Vulkan)? to ?
Optional features (extensions)? to ?not checked on both
Features that pass their check (validated)not tested on bothvulkan-805-adpkg and Balemuni_Apex_v2_ULTIMATE_SD8Gen2: no driver check yet
Speed test scenes (benchmark)1 faster 3 slower4% slower overall (geometric mean)
- hdr_2160p39% faster
- oit_linked_lists5% slower
- pipeline_barriers_2160p23% slower
- subpasses_2160p17% 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: 1694 of 2304 cells, pipeline_barriers_2160p: 1037 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 compared: 2 scenes with a paced frame rate (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.
vulkan-805-adpkg details Balemuni_Apex_v2_ULTIMATE_SD8Gen2 details
Feature checks that differ
vulkan-805-adpkg and Balemuni_Apex_v2_ULTIMATE_SD8Gen2: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.
Speed test scenes (benchmark)
| Scene | vulkan-805-adpkg ms | Balemuni_Apex_v2_ULTIMATE_SD8Gen2 ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 8.33 typical 8.33 | n/a | only one side | 3 of 3 vs 0 of 3 | 950 vs ? clock unknown | not checked |
| hdr_2160p | 30.25 typical 30.20 | 21.80 typical 21.65 | 39% faster | 3 of 3 vs 3 of 3 | 950 vs ? clock unknown | no large difference 0.0 no small difference worst 0.3 64x36 |
| oit_linked_lists | 19.31 typical 19.33 | 20.37 typical 20.39 | 5% slower | 3 of 3 vs 3 of 3 | 875 vs ? clock unknown | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | paced at 5.55 | 3.51 typical 3.38 | too light, see pipeline_barriers_2160p | 3 of 3 vs 3 of 3 | 611 vs ? clock unknown | no large difference 9.3 differs in 1694 small areas worst 47.3 64x36 |
| pipeline_barriers_2160p | 10.70 typical 10.73 | 13.92 typical 13.51 | 23% slower | 3 of 3 vs 3 of 3 | 950 vs ? clock unknown | no large difference 6.4 differs in 1037 small areas worst 51.7 64x36 |
| subpasses | paced at 5.56 | 5.46 typical 5.28 | too light, see subpasses_2160p | 3 of 3 vs 3 of 3 | 950 vs ? clock unknown | not checked |
| subpasses_2160p | 17.92 typical 17.90 | 21.57 typical 21.53 | 17% slower | 3 of 3 vs 3 of 3 | 950 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 Balemuni_Apex_v2_ULTIMATE_SD8Gen2 against vulkan-805-adpkg. "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.