Home / Mali-G610 / Compare

Mali-G610 MC6 vs Mali-G610 MC6

On Mali-G610 (GameForce Ace, Infinix GT 20 Pro, Infinix NOTE Edge, Nothing Phone (2a) Plus, realme 真我 GT NEO 3 150W, Vivo V27, Xiaomi 13T). The first driver named is compared against the second, which is the baseline.

StockMali-G610 MC6v1.r32p1-01eac0.b89152572cfa9465230812a8225a45a0

CustomMali-G610 MC6v1.r38p1-01eac0.91ad9bb3ee6ee6b8afda80c5afcd3137

Graphics system version (Vulkan)1.1.177 to 1.1.219

Optional features (extensions)71 to 93+22 -0

Features that pass their check (validated)31 to 321 pass only on Mali-G610 MC6 0 pass only on Mali-G610 MC6

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

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

hdr_2160p15% faster
oit_linked_lists10% faster
pipeline_barriers11% faster
subpasses24% faster

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: 1420 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

Mali-G610 MC6 details Mali-G610 MC6 details

Feature checks that differ (3)

Feature	Stock	Mali-G610 MC6	Change
extendedDynamicState2 VK_EXT_extended_dynamic_state2	unsupported	pass	gained
extendedDynamicState VK_EXT_extended_dynamic_state	unsupported	fail	changed
extendedDynamicState2PatchControlPoints VK_EXT_extended_dynamic_state2	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-G610 MC6 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	17.56	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
hdr_2160p	27.32 typical 27.39	23.78 typical 23.62	15% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
oit_linked_lists	21.38 typical 21.20	19.35 typical 19.19	10% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers	8.42 typical 8.35	7.59 typical 7.57	11% faster	3 of 3 vs 3 of 3	? vs ? clock unknown	no large difference 6.8 differs in 1420 small areas worst 43.3 64x36
pipeline_barriers_2160p	n/a	22.52 typical 22.55	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
subpasses	16.43 typical 16.49	13.26 typical 13.24	24% faster	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 Mali-G610 MC6 against Mali-G610 MC6. "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-G610 MC6 (22)

VK_ARM_rasterization_order_attachment_access
VK_EXT_extended_dynamic_state
VK_EXT_extended_dynamic_state2
VK_EXT_global_priority_query
VK_EXT_image_compression_control
VK_EXT_load_store_op_none
VK_EXT_multisampled_render_to_single_sampled
VK_EXT_pipeline_creation_cache_control
VK_EXT_pipeline_creation_feedback
VK_EXT_primitive_topology_list_restart
VK_EXT_primitives_generated_query
VK_EXT_private_data
VK_EXT_rgba10x6_formats
VK_EXT_shader_demote_to_helper_invocation
VK_EXT_subpass_merge_feedback
VK_EXT_texel_buffer_alignment
VK_EXT_tooling_info
VK_KHR_copy_commands2
VK_KHR_shader_integer_dot_product
VK_KHR_shader_terminate_invocation
VK_KHR_synchronization2
VK_KHR_zero_initialize_workgroup_memory

Extensions only in Mali-G610 MC6 (0)

None

Core features that differ (0)

None

Limits that differ (5)

Limit	Stock	Mali-G610 MC6
maxMemoryAllocationCount	4294967295	16384
bufferImageGranularity	4096	1
maxBoundDescriptorSets	4	7
maxGeometryInputComponents	64	128
maxGeometryTotalOutputComponents	1024	2048

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

Only in Mali-G610 MC6:

A2R10G10B10_SSCALED_PACK32
A2R10G10B10_USCALED_PACK32
B8G8R8A8_SSCALED
B8G8R8A8_USCALED
B8G8R8_SSCALED
B8G8R8_USCALED

Only in Mali-G610 MC6:

None