← VLSI Museum

SOURCE-LINKED COMPARISON

Kirin 810 vs Kirin 990 5G

GPU description: Kirin 810 Mali-G52; Kirin 990 5G Mali-G76. A sourced specification comparison.

Kirin 810 and Kirin 990 5G are compared as product models in the same soc cohort. CPU cores: Kirin 810 lists 8; Kirin 990 5G lists 8. Architecture: Kirin 810 lists Cortex-A76; Kirin 990 5G lists Cortex-A76. The listed organization describes the documented configuration; it does not rank application speed.

Memory technology: Kirin 810 lists LPDDR4X-4266; Kirin 990 5G lists LPDDR4X-4266. Memory bandwidth: Kirin 810 lists 31.78 GiB/s; Kirin 990 5G lists 31.78 GiB/s. Process label: Kirin 810 lists 7 nm; Kirin 990 5G lists 7 nm+ EUV. GPU description: Kirin 810 lists Mali-G52; Kirin 990 5G lists Mali-G76. The GPU and memory descriptions help identify the documented graphics and data interfaces. Process names and nominal limits require their original source context.

This comparison matches 10 sourced fields across 4 specification sections. 2 fields differ. 0 of 20 field values use manufacturer disclosures; remaining values retain their source evidence class. The field publication dates remain attached to their sources. There is no matched measured workload benchmark or current price evidence in this page, so it cannot establish a purchase winner, energy-efficiency winner or total system cost.

Documented differences

Specification / evidenceKirin 810product-model · socKirin 990 5Gproduct-model · soc
CPU coresOrganization and listed limits do not establish workload performance.8Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{chip}} / core count8Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{chip}} / core count
CPU threadsRead the original field scope, conditions and source before comparing.8Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{chip}} / thread count8Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{chip}} / thread count
GPU descriptionOrganization and listed limits do not establish workload performance.Mali-G52Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{integrated graphics}} / gpuMali-G76Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{integrated graphics}} / gpu
ArchitectureRead the original field scope, conditions and source before comparing.Cortex-A76Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{chip}} / microarchCortex-A76Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{chip}} / microarch
Instruction setRead the original field scope, conditions and source before comparing.ARMv8Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{chip}} / isaARMv8Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{chip}} / isa
Process labelFoundry process names are labels, not equivalent physical dimensions.7 nmScope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{chip}} / process7 nm+ EUVScope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{chip}} / process
Maximum supported memoryRead the original field scope, conditions and source before comparing.8 GiBScope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{memory controller}} / max mem8 GiBScope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{memory controller}} / max mem
Memory bandwidthOrganization and listed limits do not establish workload performance.31.78 GiB/sScope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{memory controller}} / max bandwidth31.78 GiB/sScope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{memory controller}} / max bandwidth
Memory channelsRead the original field scope, conditions and source before comparing.4Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{memory controller}} / channels4Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{memory controller}} / channels
Memory technologyRead the original field scope, conditions and source before comparing.LPDDR4X-4266Scope: product-modelEvidence: third-party-reportSource date: 2021-10-25Source: chipswiki-584-r1342 · Hisilicon/kirin/810 · revision 1342 · {{memory controller}} / typeLPDDR4X-4266Scope: product-modelEvidence: third-party-reportSource date: 2022-05-26Source: chipswiki-348-r731 · Kirin 990 · revision 731 · {{memory controller}} / type

Who should consider each?

Use the soc specifications to check the intended integration requirements. For a purchase, add current availability, price, software compatibility and measurements of your workload. The field differences alone do not justify recommending one model.

Related records

Sources

  1. Kirin 990 5G — ChipsWiki, revision 731 · ChipsWiki / WikiChip contributors · 2022-05-26 · CC BY-NC-SA 4.0
  2. Kirin 810 — ChipsWiki, revision 1342 · ChipsWiki / WikiChip contributors · 2021-10-25 · CC BY-NC-SA 4.0

A specification difference is not a measured workload result. Sources and entity scope must match before drawing performance conclusions.