FauxVkDB
English
Home / Mali-G52 / Compare

panvk-g76-armsx2-v9 vs panvk-g76-kirin990-1.2.3

On Mali-G52 (CHUWI HiPad-Air, HONOR X5c, HONOR X5c, Infinix HOT 60i, Oppo A18, Oppo A38, realme RMX3710, Redmi 12, Redmi 12C, Redmi 14C, Redmi 15C, Samsung Galaxy A32, TECNO POVA 3, TECNO SPARK 10 Pro, TECNO SPARK 20, Vivo Y03, Xiaomi 24049RN28L). The first driver named is compared against the second, which is the baseline.

Stockpanvk-g76-kirin990-1.2.3PanVK-kbase G76-k990 1.2.3 (Mesa 26.3.0-devel (git-e53ed5c178))
vs
Custompanvk-g76-armsx2-v9Mesa 26.3.0-devel (git-d097871eb9)
Graphics system version (Vulkan)1.3.363 to 1.3.354
Optional features (extensions)165 to 160+5 -10
Features that pass their check (validated)63 to 390 pass only on panvk-g76-armsx2-v9 24 pass only on panvk-g76-kirin990-1.2.3
Speed test scenes (benchmark)0 faster 3 slower31% slower 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
  • compute_nbody24% slower
  • pipeline_barriers37% slower
  • subpasses30% 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: 2 of 2304 cells, pipeline_barriers: 1528 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.

Did not start every time: hdr_2160p (stock 3 of 3, custom 0 of 3).

panvk-g76-kirin990-1.2.3 details panvk-g76-armsx2-v9 details

Feature checks that differ (34)

Featurepanvk-g76-kirin990-1.2.3panvk-g76-armsx2-v9Change
robustBufferAccess2
VK_EXT_robustness2
passunsupportedlost
robustImageAccess2
VK_EXT_robustness2
passunsupportedlost
transformFeedback
VK_EXT_transform_feedback
passunsupportedlost
shaderBufferInt64Atomics
VK_KHR_shader_atomic_int64
passunsupportedlost
depthClamp
VkPhysicalDeviceFeatures
passuntestedlost
geometryShader
VkPhysicalDeviceFeatures
passcrashlost
largePoints
VkPhysicalDeviceFeatures
passuntestedlost
multiDrawIndirect
VkPhysicalDeviceFeatures
passfaillost
occlusionQueryPrecise
VkPhysicalDeviceFeatures
passfaillost
tessellationShader
VkPhysicalDeviceFeatures
passfaillost
textureCompressionBC
VkPhysicalDeviceFeatures
passunsupportedlost
compat.helper_loop_terminator
core
passuntestedlost
core.blend_advertised_formats
core
passuntestedlost
core.compute_big_stack
core
passuntestedlost
core.host_coherent_readback
core
passuntestedlost
core.mrt_partial_kill
core
passuntestedlost
core.ubo_update_buffer
core
passuntestedlost
core.ubo_written_after_record
core
passuntestedlost
core.varying_subset
core
passuntestedlost
mem.image_padding
core
passuntestedlost
push.max_combined_image_samplers
core
passcrashlost
stage.geometry_max_output
core
passuntestedlost
stage.geometry_point_size
core
passuntestedlost
sync.first_submit_clear_then_compute
core
passuntestedlost
customBorderColorWithoutFormat
VK_EXT_custom_border_color
untestedunsupportedchanged
extendedDynamicState2PatchControlPoints
VK_EXT_extended_dynamic_state2
untestedunsupportedchanged
nullDescriptor
VK_EXT_robustness2
untestedunsupportedchanged
geometryStreams
VK_EXT_transform_feedback
untestedunsupportedchanged
shaderSharedInt64Atomics
VK_KHR_shader_atomic_int64
untestedunsupportedchanged
depthBounds
VkPhysicalDeviceFeatures
untestedunsupportedchanged
pipelineStatisticsQuery
VkPhysicalDeviceFeatures
untestedunsupportedchanged
variableMultisampleRate
VkPhysicalDeviceFeatures
untestedunsupportedchanged
vertexPipelineStoresAndAtomics
VkPhysicalDeviceFeatures
untestedunsupportedchanged
compat.nested_map
core
failuntestedchanged

Speed test scenes (benchmark)

unverified panvk-g76-kirin990-1.2.3: The times below were sent from a device this site could not confirm. A result the site counts replaces them.

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-g76-kirin990-1.2.3 mspanvk-g76-armsx2-v9 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody79.10 typical 77.34104.48 typical 104.2824% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.1 differs in 2 small areas worst 4.7 64x36
hdr_2160p160.79 typical 156.92n/aonly one side3 of 3 vs 0 of 3? vs ? clock unknownnot checked
oit_linked_lists104.24n/aonly one side3 of 3 vs 3 of 3? vs ? clock unknownno large difference 0.0 no small difference worst 0.0 64x36
pipeline_barriers64.07 typical 63.49101.82 typical 101.5437% slower3 of 3 vs 3 of 3? vs ? clock unknownno large difference 9.9 differs in 1528 small areas worst 91.0 64x36
subpasses116.18 typical 116.69165.26 typical 164.2230% slower3 of 3 vs 3 of 3? 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-g76-armsx2-v9 against panvk-g76-kirin990-1.2.3. "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-g76-armsx2-v9 (5)
  • VK_ARM_rasterization_order_attachment_access
  • VK_EXT_multisampled_render_to_single_sampled
  • VK_EXT_rasterization_order_attachment_access
  • VK_KHR_depth_clamp_zero_one
  • VK_KHR_pipeline_binary
Extensions only in panvk-g76-kirin990-1.2.3 (10)
  • VK_EXT_astc_decode_mode
  • VK_EXT_conditional_rendering
  • VK_EXT_descriptor_indexing
  • VK_EXT_image_compression_control
  • VK_EXT_mutable_descriptor_type
  • VK_EXT_robustness2
  • VK_EXT_transform_feedback
  • VK_KHR_shader_atomic_int64
  • VK_KHR_shader_constant_data
  • VK_VALVE_mutable_descriptor_type
Core features that differ (3)
shaderBufferInt64Atomics Vulkan 1.2pass to unsupported
shaderOutputViewportIndex Vulkan 1.2pass to unsupported
shaderSharedInt64Atomics Vulkan 1.2pass to unsupported
Limits that differ (10)
Limitpanvk-g76-kirin990-1.2.3panvk-g76-armsx2-v9
sparseAddressSpaceSize171463147520
maxBoundDescriptorSets74
maxGeometryOutputComponents12864
maxFragmentDualSrcAttachments18
maxDrawIndirectCount655354294967295
timestampComputeAndGraphics10
timestampPeriod76.92310
maxClipDistances80
maxCullDistances80
maxCombinedClipAndCullDistances80
Formats supported by only one driver (0 gained, 8 lost)

Only in panvk-g76-armsx2-v9:

  • None

Only in panvk-g76-kirin990-1.2.3:

  • BC4_SNORM_BLOCK
  • BC4_UNORM_BLOCK
  • BC5_SNORM_BLOCK
  • BC5_UNORM_BLOCK
  • BC6H_SFLOAT_BLOCK
  • BC6H_UFLOAT_BLOCK
  • BC7_SRGB_BLOCK
  • BC7_UNORM_BLOCK