FauxVkDB
English
Home / Mali-G68 / Compare

Mali-G68 vs Mali-G68

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

StockMali-G68v1.r38p1-01eac0-mbs2v41_0.8afb03e9a27ca831737e7b78bf21f6ee
vs
CustomMali-G68v1.r38p1-01eac0-mbs2v41_0.0b37450fbb12e582df79a7906d0ad856
Graphics system version (Vulkan)1.3.219 to 1.3.219
Optional features (extensions)96 to 97+1 -0
Features that pass their check (validated)29 to 29both pass the same checks
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 details Mali-G68 details

Feature checks that differ (0)

Every feature check ends the same way on both drivers.

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.

SceneStock msMali-G68 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody45.93 typical 45.63n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
hdr_2160p134.23 typical 134.05n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
oit_linked_lists31.14 typical 30.74n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
pipeline_barriers30.65 typical 30.83n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
subpasses65.35 typical 65.34n/aonly one side3 of 3 vs ?? 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 Mali-G68 against Mali-G68. "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 (1)
  • VK_EXT_hdr_metadata
Extensions only in Mali-G68 (0)
  • None
Core features that differ (0)
None
Limits that differ (0)
LimitStockMali-G68
Formats supported by only one driver (0 gained, 0 lost)

Only in Mali-G68:

  • None

Only in Mali-G68:

  • None