Home / Mali-G720 MC7 / Compare

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

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

StockPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATORv1.r49p1-03bet0.4fc328bba6e40f10f4bc96d62f5ee40a

CustomPanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATORv1.r49p1-03bet0.4fc328bba6e40f10f4bc96d62f5ee40a

Graphics system version (Vulkan)? to ?

Optional features (extensions)? 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 and PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATOR: no driver check yet

Speed test scenes (benchmark)1 faster 0 slower 1 even1% faster overall (geometric mean)

compute_nbody2% faster
hdr_2160p1% 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 1 scene (pipeline_barriers: 1157 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

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-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR details PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATOR details

Feature checks that differ

PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR and PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-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)

unverified PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATOR: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

Scene	PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR ms	PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATOR ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	16.31 typical 16.21	15.96 typical 15.90	2% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
hdr_2160p	18.21 typical 18.07	18.38 typical 18.27	1% slower	? vs 3 of 3	? vs ? clock unknown	not checked
oit_linked_lists	22.41	n/a	only one side	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	paced at 8.30	8.29 typical 8.19	not compared	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 6.7 differs in 1157 small areas worst 50.0 64x36
subpasses	paced at 8.32	n/a	not compared	3 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 PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-lowmem-5a07217f-EMULATOR 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.