FauxVkDB
English
Home / Mali-G52 MC2 / Compare

PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools vs Panvk-Mali-G57-3.0

On Mali-G52 MC2 (HONOR X5c, HONOR X5c, Infinix HOT 60i, Oppo A18, Oppo A38, realme RMX3710, Redmi 12, Redmi 12C, Redmi 14C, Redmi 15C, TECNO POVA 3, TECNO SPARK 20, Xiaomi 24049RN28L). The first driver named is compared against the second, which is the baseline.

StockPanvk-Mali-G57-3.0FristOneRR 3.0 (Mesa 26.3.0-devel)
vs
CustomPanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotoolsPanVK-kbase RC4 (Mesa 26.3.0-devel (git-5a07217f03))
Graphics system version (Vulkan)1.3.354 to 1.3.363
Optional features (extensions)140 to 159+20 -1
Features that pass their check (validated)39 to 380 pass only on PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools 1 pass only on Panvk-Mali-G57-3.0
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

Panvk-Mali-G57-3.0 details PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools details

Feature checks that differ (6)

FeaturePanvk-Mali-G57-3.0PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotoolsChange
push.max_combined_image_samplers
core
passcrashlost
fillModeNonSolid
VkPhysicalDeviceFeatures
untestedunsupportedchanged
geometryShader
VkPhysicalDeviceFeatures
failunsupportedchanged
multiViewport
VkPhysicalDeviceFeatures
untestedunsupportedchanged
shaderClipDistance
VkPhysicalDeviceFeatures
untestedunsupportedchanged
shaderCullDistance
VkPhysicalDeviceFeatures
untestedunsupportedchanged

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.

ScenePanvk-Mali-G57-3.0 msPanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody87.85 typical 86.94n/aonly one side2 of 3 vs ?? vs ? clock unknownnot checked
hdr_2160p149.04 typical 148.57n/aonly one side0 of 3 vs ?? vs ? clock unknownnot checked
oit_linked_lists77.01 typical 78.56n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
pipeline_barriers91.08 typical 92.10n/aonly one side3 of 3 vs ?? vs ? clock unknownnot checked
subpasses140.70 typical 139.35n/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 PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools against Panvk-Mali-G57-3.0. "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 PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools (20)
  • VK_EXT_astc_decode_mode
  • VK_EXT_graphics_pipeline_library
  • VK_EXT_image_compression_control
  • VK_EXT_map_memory_placed
  • VK_EXT_present_timing
  • VK_GOOGLE_user_type
  • VK_KHR_internally_synchronized_queues
  • VK_KHR_maintenance7
  • VK_KHR_maintenance8
  • VK_KHR_maintenance9
  • VK_KHR_present_id
  • VK_KHR_present_id2
  • VK_KHR_present_wait
  • VK_KHR_present_wait2
  • VK_KHR_shader_constant_data
  • VK_KHR_shader_fma
  • VK_KHR_shader_relaxed_extended_instruction
  • VK_KHR_swapchain_maintenance1
  • VK_KHR_swapchain_mutable_format
  • VK_KHR_unified_image_layouts
Extensions only in Panvk-Mali-G57-3.0 (1)
  • VK_EXT_external_memory_host
Core features that differ (0)
None
Limits that differ (3)
LimitPanvk-Mali-G57-3.0PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools
sparseAddressSpaceSize017146314752
maxBoundDescriptorSets47
maxFragmentDualSrcAttachments81
Formats supported by only one driver (0 gained, 0 lost)

Only in PanVK-Kbase-Android-v0.1.0-rc4-5a07217f-adrenotools:

  • None

Only in Panvk-Mali-G57-3.0:

  • None