Home / Mali-G52 / Compare

malisx2-0.3.3-d0422ed5eb vs PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR

On Mali-G52 (CHUWI HiPad-Air, HONOR X5c, HONOR X5c, Infinix HOT 60i, Oppo A18, Oppo A38, realme RMX3710, Redmi 12, Redmi 12, Redmi 12C, Redmi 13C, Redmi 14C, Redmi 15C, Redmi A3 Pro, Samsung Galaxy A32, Samsung Galaxy Tab A8, TECNO POVA 3, TECNO SPARK 10 Pro, TECNO SPARK 20, Vivo Y03, Xiaomi 24040RN64Y, Xiaomi 24049RN28L). 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.19498e0ae1d5dac223383c39a2e58f04

Custommalisx2-0.3.3-d0422ed5ebv1.r44p1-malisx2.0.3.3.s2cfdc5a55fc8

Graphics system version (Vulkan)1.3.278 to ?

Optional features (extensions)131 to ?not checked on both

Features that pass their check (validated)not tested on bothmalisx2-0.3.3-d0422ed5eb: no driver check yet

Speed test scenes (benchmark)0 faster 4 slower17% slower overall (geometric mean)

compute_nbody22% slower
oit_linked_lists12% slower
pipeline_barriers23% slower
subpasses13% 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 (compute_nbody: 36 of 2304 cells, pipeline_barriers: 1418 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR details malisx2-0.3.3-d0422ed5eb details

Feature checks that differ

malisx2-0.3.3-d0422ed5eb: no driver check (validation report) yet. Both drivers need a driver check before their feature checks can be compared.

Speed test scenes (benchmark)

Scene	PanVK-Kbase-g615-v11-csf-v0.1.0-rc3-5a07217f-EMULATOR ms	malisx2-0.3.3-d0422ed5eb ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	81.47 typical 81.85	103.83 typical 103.47	22% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.2 differs in 36 small areas worst 8.3 64x36
oit_linked_lists	67.79 typical 67.63	76.64 typical 76.40	12% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	66.90 typical 67.96	87.13 typical 88.80	23% slower	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 10.1 differs in 1418 small areas worst 90.3 64x36
subpasses	127.99 typical 128.74	147.07 typical 146.49	13% slower	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 malisx2-0.3.3-d0422ed5eb 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.