FauxVkDB
English
Home / Mali-G720 MC7 / Compare

PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR vs panvk_faux123_ace_v0.36.0

On Mali-G720 MC7 (POCO X7 Pro, POCO X8 Pro). The first driver named is compared against the second, which is the baseline.

Stockpanvk_faux123_ace_v0.36.0PanVK-kbase beta.14 (Mesa 26.3.0-devel (git-5a07217f03))
vs
CustomPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATORv1.r49p1-03bet0.4fc328bba6e40f10f4bc96d62f5ee40a
Graphics system version (Vulkan)1.4.363 to ?
Optional features (extensions)188 to ?not checked on both
Features that pass their check (validated)not tested on bothPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR: no driver check yet
Speed test scenes (benchmark)none comparable

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.

panvk_faux123_ace_v0.36.0 details PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR details

Feature checks that differ

PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

Scenepanvk_faux123_ace_v0.36.0 msPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbodyn/a16.31 typical 16.21only one side? vs 3 of 3? vs ? clock unknownnot checked
hdr_2160pn/a18.21 typical 18.07only one side? vs ?? vs ? clock unknownnot checked
oit_linked_listsn/a22.59 typical 22.41only one side? vs 3 of 3? vs ? clock unknownnot checked
pipeline_barriersn/apaced at 8.30not compared? vs 3 of 3? vs ? clock unknownnot checked
subpassesn/apaced at 8.32not compared? 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 PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR against panvk_faux123_ace_v0.36.0. "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.