← VLSI Museum

SOURCE-LINKED COMPARISON

Dimensity 1000 vs Snapdragon 865

GPU description: Dimensity 1000 Mali-G77; Snapdragon 865 Adreno 650 GPU. A sourced specification comparison.

Dimensity 1000 and Snapdragon 865 are compared as product models in the same soc cohort. CPU cores: Dimensity 1000 lists 8; Snapdragon 865 lists 8. Architecture: Dimensity 1000 lists Cortex-A77; Snapdragon 865 lists Cortex-A77. The listed organization describes the documented configuration; it does not rank application speed.

Memory bandwidth: Dimensity 1000 lists 29.87 GiB/s; Snapdragon 865 lists 40.98 GiB/s. Maximum supported memory: Dimensity 1000 lists 16 GiB; Snapdragon 865 lists 16 GiB. Instruction set: Dimensity 1000 lists ARMv8.2-A; Snapdragon 865 lists ARMv8. Process label: Dimensity 1000 lists 7 nm; Snapdragon 865 lists 7 nm. GPU description: Dimensity 1000 lists Mali-G77; Snapdragon 865 lists Adreno 650 GPU. 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 9 sourced fields across 4 specification sections. 3 fields differ. 0 of 18 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 / evidenceDimensity 1000product-model · socSnapdragon 865product-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 count8Scope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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 count8Scope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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}} / gpuAdreno 650 GPUScope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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}} / microarchCortex-A77Scope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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}} / isaARMv8Scope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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}} / process7 nmScope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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 memory16 GiBScope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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 bandwidth40.98 GiB/sScope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{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}} / channels4Scope: product-modelEvidence: third-party-reportSource date: 2022-02-10Source: chipswiki-514-r1036 · Qualcomm/snapdragon 800/865 · revision 1036 · {{memory controller}} / channels

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. Dimensity 1000 — ChipsWiki, revision 3057 · ChipsWiki / WikiChip contributors · 2020-07-03 · CC BY-NC-SA 4.0
  2. Snapdragon 865 — ChipsWiki, revision 1036 · ChipsWiki / WikiChip contributors · 2022-02-10 · 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.