Home / Mali-G68 / Compare

Mali-G68 MC4 vs Mali-G68 MC4

On Mali-G68 (Infinix ZERO 5G 2023, LENOVO TB370FU, realme 10 Pro+ 5G, realme P1 5G, Samsung Galaxy A16 5G, Samsung Galaxy A16 5G, Samsung Galaxy A16 5G, Samsung Galaxy A17 5G, Samsung Galaxy A25 5G, Samsung Galaxy A26 5G, Samsung Galaxy A33 5G, Samsung Galaxy A34 5G, Samsung Galaxy A53 5G, Samsung Galaxy A54 5G, vivo V2202). The first driver named is compared against the second, which is the baseline.

StockMali-G68 MC4v1.r49p1-03bet0.3666fcaacb504f548df1f5efc729b42d

CustomMali-G68 MC4v1.r49p1-03bet0.5f9a92adb22346da069f00be2943f72a

Graphics system version (Vulkan)1.3.278 to 1.3.278

Optional features (extensions)138 to 138+1 -1

Features that pass their check (validated)56 to 370 pass only on Mali-G68 MC4 19 pass only on Mali-G68 MC4

Speed test scenes (benchmark)no shared scenes

Games each driver could run (an estimate from its feature list): green likely, yellow maybe, orange limited, red no

StockDX92002+DX102006+DX112009+DX122015+Switch

CustomDX92002+DX102006+DX112009+DX122015+Switch

Mali-G68 MC4 details Mali-G68 MC4 details

Feature checks that differ (20)

Feature	Stock	Mali-G68 MC4	Change
depthClamp VkPhysicalDeviceFeatures	pass	untested	lost
largePoints VkPhysicalDeviceFeatures	pass	untested	lost
compat.helper_loop_terminator core	pass	untested	lost
compat.nested_map core	pass	untested	lost
core.blend_advertised_formats core	pass	untested	lost
core.compute_big_stack core	pass	untested	lost
core.host_coherent_readback core	pass	untested	lost
core.mrt_partial_kill core	pass	untested	lost
core.ubo_update_buffer core	pass	untested	lost
core.ubo_written_after_record core	pass	untested	lost
core.varying_subset core	pass	untested	lost
mem.image_padding core	pass	untested	lost
perf.fb_local_barrier_large_draws core	pass	untested	lost
perf.fb_local_barrier_overdraw core	pass	untested	lost
stage.geometry_max_output core	pass	untested	lost
stress.many_command_buffers_one_submit core	pass	untested	lost
stress.scratch_per_batch core	pass	untested	lost
stress.spill_helper_lanes core	pass	untested	lost
sync.first_submit_clear_then_compute core	pass	untested	lost
stage.geometry_point_size core	unsupported	untested	changed

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	Mali-G68 MC4 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
hdr_2160p	n/a	75.30 typical 75.32	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
oit_linked_lists	n/a	26.63 typical 26.79	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
pipeline_barriers	n/a	15.92 typical 15.94	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
subpasses	n/a	n/a	only one side	? 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 Mali-G68 MC4 against Mali-G68 MC4. "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)

Extensions only in Mali-G68 MC4 (1)

VK_EXT_hdr_metadata

Extensions only in Mali-G68 MC4 (1)

VK_KHR_swapchain_mutable_format

Core features that differ (0)

None

Limits that differ (0)

Limit	Stock	Mali-G68 MC4

Formats supported by only one driver (0 gained, 0 lost)

Only in Mali-G68 MC4:

None

Only in Mali-G68 MC4:

None