SOURCE-LINKED COMPARISON
Dimensity 1000 vs Dimensity 800
GPU description: Dimensity 1000 Mali-G77; Dimensity 800 Mali-G57. A sourced specification comparison.
Dimensity 1000 and Dimensity 800 are compared as product models in the same soc cohort. CPU cores: Dimensity 1000 lists 8; Dimensity 800 lists 8. Architecture: Dimensity 1000 lists Cortex-A77; Dimensity 800 lists Cortex-A76. The listed organization describes the documented configuration; it does not rank application speed.
Memory technology: Dimensity 1000 lists LPDDR4X-3733; Dimensity 800 lists LPDDR4X-4266. Memory bandwidth: Dimensity 1000 lists 29.87 GiB/s; Dimensity 800 lists 17.07 GiB/s. Memory channels: Dimensity 1000 lists 4; Dimensity 800 lists 2. Process label: Dimensity 1000 lists 7 nm; Dimensity 800 lists 7 nm. GPU description: Dimensity 1000 lists Mali-G77; Dimensity 800 lists Mali-G57. 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. 5 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 / evidence | Dimensity 1000product-model · soc | Dimensity 800product-model · soc |
|---|---|---|
| CPU coresOrganization and listed limits do not establish workload performance. | 8Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / core count | 8Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / core count |
| CPU threadsRead the original field scope, conditions and source before comparing. | 8Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / thread count | 8Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / thread count |
| GPU descriptionOrganization and listed limits do not establish workload performance. | Mali-G77Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{integrated graphics}} / gpu | Mali-G57Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{integrated graphics}} / gpu |
| ArchitectureRead the original field scope, conditions and source before comparing. | Cortex-A77Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / microarch | Cortex-A76Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / microarch |
| Instruction setRead the original field scope, conditions and source before comparing. | ARMv8.2-AScope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / isa | ARMv8.2-AScope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / isa |
| Process labelFoundry process names are labels, not equivalent physical dimensions. | 7 nmScope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / process | 7 nmScope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / process |
| Maximum supported memoryRead the original field scope, conditions and source before comparing. | 16 GiBScope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{chip}} / max memory | 16 GiBScope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{chip}} / max memory |
| Memory bandwidthOrganization and listed limits do not establish workload performance. | 29.87 GiB/sScope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{memory controller}} / max bandwidth | 17.07 GiB/sScope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{memory controller}} / max bandwidth |
| Memory channelsRead the original field scope, conditions and source before comparing. | 4Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{memory controller}} / channels | 2Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{memory controller}} / channels |
| Memory technologyRead the original field scope, conditions and source before comparing. | LPDDR4X-3733Scope: product-modelEvidence: third-party-reportSource date: 2020-07-03Source: chipswiki-1064-r3057 · Mediatek/dimensity/1000 · revision 3057 · {{memory controller}} / type | LPDDR4X-4266Scope: product-modelEvidence: third-party-reportSource date: 2021-01-31Source: chipswiki-832-r2147 · Mediatek/dimensity/800 · revision 2147 · {{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
- Dimensity 1000 — ChipsWiki, revision 3057 · ChipsWiki / WikiChip contributors · 2020-07-03 · CC BY-NC-SA 4.0
- Dimensity 800 — ChipsWiki, revision 2147 · ChipsWiki / WikiChip contributors · 2021-01-31 · 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.