FauxVkDB
English
Home / Mali-G615 MC2 / Compare

PanVk-Valhall-LukeValen-Strato vs PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR

On Mali-G615 MC2 (HEADWOLF F8, Infinix GT 30, Infinix GT 30 Pro, motorola edge - 2026, motorola edge 60 pro, POCO X6 Pro 5G, POCO X6 Pro 5G, Redmi Note 14 Pro 5G, TECNO CAMON 40). The first driver named is compared against the second, which is the baseline.

StockPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATORv1.r44p1-01eac0.999bbcba36b4ca04774e2b05d5802dc0
vs
CustomPanVk-Valhall-LukeValen-StratoPanVK-kbase beta.18-rc2 (Mesa 26.3.0-devel (git-5a07217f03))
Graphics system version (Vulkan)1.3.247 to ?
Optional features (extensions)118 to ?not checked on both
Features that pass their check (validated)not tested on bothPanVk-Valhall-LukeValen-Strato: no driver check yet
Speed test scenes (benchmark)no shared scenes

PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR details PanVk-Valhall-LukeValen-Strato details

Feature checks that differ

PanVk-Valhall-LukeValen-Strato: 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.

ScenePanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR msPanVk-Valhall-LukeValen-Strato msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody17.32 typical 16.72n/aonly one side3 of 3 vs 0 of 3? vs ? clock unknownnot checked
hdr_2160p36.83 typical 36.72n/aonly one side3 of 3 vs 0 of 3? vs ? clock unknownnot checked
oit_linked_lists28.50 typical 28.39n/aonly one side3 of 3 vs 0 of 3? vs ? clock unknownnot checked
pipeline_barriers8.29 typical 8.18n/aonly one side3 of 3 vs 0 of 3? vs ? clock unknownnot checked
pipeline_barriers_2160p13.75 typical 13.76n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
subpasses14.20 typical 14.10n/aonly one side3 of 3 vs 0 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 PanVk-Valhall-LukeValen-Strato against PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR. "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.