Qualcomm_840_adpkg vs Qualcomm Technologies Inc. Adreno Vulkan Driver
On Adreno (TM) 740 (AYN Odin2, AYN Odin2 Portal, AYN Thor, Moorechip Retroid Pocket Nova, motorola edge plus 2023, OnePlus 11 5G, POCO F6 Pro, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23 Ultra, Samsung Galaxy S23 Ultra, Samsung Galaxy S23+, Sony Xperia 1 V, Xiaomi 13 pro). The first driver named is compared against the second, which is the baseline.
StockQualcomm Technologies Inc. Adreno Vulkan DriverDriver Build: 69e13475cb, I1df7ad3aa9, 1703680572
vsCustomQualcomm_840_adpkgDriver Build: 823f27cb7c, Ic944e09b26, 1753107019
Graphics system version (Vulkan)1.3.128 to ?
Optional features (extensions)113 to ?not checked on both
Features that pass their check (validated)not tested on bothQualcomm_840_adpkg: no driver check yet
Speed test scenes (benchmark)1 faster 1 slower 1 even7% slower overall (geometric mean)
- hdr_2160p23% slower
- oit_linked_lists1% faster
- subpasses_2160p5% 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 2 scenes (pipeline_barriers: 1357 of 2304 cells, pipeline_barriers_2160p: 1567 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 1 of these scenes (for example subpasses_2160p: stock at 100% of the device's maximum, custom at 93%). Part of the frame-time difference comes from the clock the device chose, not from the driver.
Not compared: 4 scenes with a paced frame rate (compute_nbody, pipeline_barriers, pipeline_barriers_2160p, 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 Qualcomm_840_adpkg details
Feature checks that differ
Qualcomm_840_adpkg: 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 | Stock ms | Custom ms | Difference | Starts | GPU clock, MHz | Picture vs stock |
|---|
| compute_nbody | 7.17 typical 7.06 | paced at 8.33 | not compared | 3 of 3 vs 3 of 3 | 626 vs 488 not comparable | no large difference 0.0 no small difference worst 0.0 64x36 |
| compute_nbody_2x | 20.34 typical 20.35 | n/a | only one side | 3 of 3 vs ? | 680 vs ? clock unknown | not checked |
| hdr_2160p | 21.44 typical 21.40 | 27.79 typical 27.76 | 23% slower | 3 of 3 vs 3 of 3 | 680 vs 680 | no large difference 0.0 no small difference worst 0.0 64x36 |
| oit_linked_lists | 25.48 typical 25.43 | 25.30 typical 25.26 | 1% faster | 3 of 3 vs 3 of 3 | 680 vs 680 | no large difference 0.0 no small difference worst 0.0 64x36 |
| pipeline_barriers | 3.23 typical 2.76 | paced at 5.53 | not compared | 3 of 3 vs 3 of 3 | 626 vs 413 not comparable | no large difference 7.6 differs in 1357 small areas worst 57.0 64x36 |
| pipeline_barriers_2160p | 8.08 typical 8.10 | paced at 8.35 | not compared | 3 of 3 vs 3 of 3 | 680 vs 634 not comparable | no large difference 8.9 differs in 1567 small areas worst 48.7 64x36 |
| subpasses | 4.13 typical 3.87 | paced at 5.50 | too light, see subpasses_2160p | 3 of 3 vs 3 of 3 | 680 vs 572 not comparable | not checked |
| subpasses_2160p | 13.72 typical 13.72 | 13.13 typical 13.20 | 5% faster | 3 of 3 vs 3 of 3 | 680 vs 634 not comparable | 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 Qualcomm_840_adpkg 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.