Read SOCAMM2 Specifications: Capacity, Bandwidth, and Module Counts
To read a SOCAMM2 specification, label every number with its unit, hardware scope, and qualification before calculating anything. Capacity is not bandwidth, a maximum is not installed memory, and dividing two differently defined capacity labels does not prove a module count.
Documentation checked October 17, 2026. Worked exercises below use explicitly declared assumptions; they are not a Vera bill of materials or a hardware benchmark.
Key terms, defined first
- SOCAMM2: a memory-module format; do not confuse the physical module with the CPU or the entire server.
- Capacity: how much data can be held, expressed in bytes and a stated prefix.
- GB / GiB: decimal gigabyte / binary gibibyte. The letters are not interchangeable.
- Bandwidth: a data-transfer rate, such as GB/s; not an amount of stored data.
- Gb/s / GB/s: gigabits per second / gigabytes per second. One byte is eight bits.
- Scope: the object a number describes—one module, one CPU, a Superchip, or a rack.
- Populated capacity: memory actually fitted in a specific configuration, rather than the largest supported option.
1. Attach numbers to the right hardware level
Purpose: prevent a perfectly correct calculation from answering the wrong question. A module capacity describes one physical assembly. A CPU-memory figure describes a larger memory subsystem. A rack figure describes an even wider scope.
For a real reading exercise, NVIDIA’s Vera CPU page states up to 1.5 TB of memory and up to 1.2 TB/s of LPDDR5X memory bandwidth. The first is capacity; the second is a rate. Neither number, on its own, states how many SOCAMM2 modules are installed.
Part number · capacity per module · supported operation
Populated modules · total CPU-attached capacity · aggregate memory bandwidth
CPU and GPU counts · separate memory pools · exact configuration
NVIDIA’s Vera Rubin table gives one Vera CPU and two Rubin GPUs per Superchip, with separate CPU-memory and GPU-memory rows. That does not mean two GPU memory quantities can be added to the CPU’s LPDDR5X and treated as directly interchangeable capacity.
2. Normalize GB, GiB, TB, and TiB
Definition: decimal prefixes use powers of ten; binary prefixes use powers of two. For the exercises here, 1 GB = 109 bytes, 1 TB = 1012 bytes, 1 GiB = 230 bytes, and 1 TiB = 240 bytes. See the NIST SI-prefix table and binary-prefix definitions.
192,000,000,000 bytes
÷ 1,073,741,824
≈ 178.814 GiB
206,158,430,208 bytes
÷ 1,000,000,000
≈ 206.158 GB
Use: convert both inputs into the same byte-based unit before dividing. Caution: a memory datasheet may use a legacy convention or rounded labels. If its byte definition is not explicit, preserve the vendor’s label and mark the conversion assumption; do not silently rename GB as GiB.
3. Read bandwidth without multiplying twice
Definition: a rate has a time denominator. TB and TB/s cannot be compared as if they measure the same thing. Also check whether the quoted rate is per data pin, per module, per CPU, or a link’s aggregate rate.
9.6 gigabits/s per data pin
× 128 active data pins
÷ 8 bits per byte
= 153.6 decimal GB/s
The inputs above are declared teaching assumptions—not a verified SOCAMM2 data width or measured Vera result. They describe an ideal parallel-transfer calculation. A supported module, controller, and operating configuration must actually satisfy those assumptions before the result can describe hardware.
If the input is already a transfer rate, do not apply another “double data rate” multiplier. If it is already an aggregate GB/s figure, do not multiply it by bus width again. Likewise, a CPU’s memory-bandwidth number and its CPU–GPU link-bandwidth number describe different interfaces; adding them does not create a useful memory-throughput specification.
4. Calculate a module count only when inputs match
Purpose: estimate physical modules only from a specified, compatible population—not from unrelated maximum-capacity headlines.
CPU populated memory: exactly 1.5 TiB
Identical compatible modules: 192 GiB each
1.5 × 1,024 = 1,536 GiB
1,536 ÷ 192 = 8 modules
This answer is valid only under those assumptions. It does not establish Vera’s populated module count. By contrast, blindly dividing decimal 1.5 TB by decimal 192 GB gives 7.8125. Rounding that to eight would conceal a mismatch; eight such decimal modules would total 1.536 TB, not exactly 1.5 TB.
Confirm the supported densities, population rules, and installed option with the system vendor. Do not assume one physical module equals one independently active memory channel; check the actual mapping in the controller and module documentation.
5. Use a dated specification worksheet
Definition: a specification worksheet is a small record of what the source actually says. Fill these fields before comparing products:
- Object: exact product, configuration, and revision.
- Metric: capacity, transfer rate, physical count, or another quantity.
- Unit and scope: retain the printed unit; note per module, CPU, or system.
- Qualification: “up to,” maximum supported, populated, or measured.
- Source and date: the original statement’s date plus your check date.
- Unknowns: byte convention, populated module count, or other missing conditions.
For example, Micron’s March 16, 2026 announcement describes 192 GB SOCAMM2 production and a platform capability of up to 2 TB per CPU. The current NVIDIA Superchip table lists up to 1.5 TB CPU memory. Record them as separately dated statements, not as one automatically compatible set of module-count inputs. Neither tells you what a particular customer bought.
For the industry implication rather than the arithmetic, our related English analysis explains why Vera’s reported memory-capacity cut is not an order-volume total. This tutorial answers the narrower task of checking a specification sheet.
6. Compare the common mistakes
| Mistake | Safer check |
|---|---|
| GB = GiB | Normalize the declared byte convention. |
| Gb/s = GB/s | Convert bits to bytes and verify the scope. |
| Maximum = installed | Ask for the populated configuration. |
| Fractional ratio → round up | Stop; check units, rounding, and compatibility. |
| Mixed dates → one BOM | Keep source revisions separate. BOM means bill of materials. |
Your next action: annotate one real specification using the six worksheet fields. If its byte convention or populated configuration is missing, the correct module-count answer is “not determined”—not a more confident multiplication.
Appendix. Verification and sources
All exercise arithmetic was checked locally. No SOCAMM2 module, Vera CPU, Rubin GPU, or memory benchmark was run. The exercise does not establish supported bus width, installed module counts, effective application bandwidth, shipments, or investment outcomes. No credentials or paid service are needed to repeat the arithmetic.
- NIST: binary prefixes and byte examples.
- NIST: decimal SI prefixes.
- NVIDIA: Vera CPU memory specifications, checked October 17, 2026.
- NVIDIA: Vera Rubin configuration table, checked October 17, 2026.
- Micron: March 16, 2026 production statement.
Original learning diagrams and worked examples by Deoks. Definitions, assumptions, and vendor specifications are kept separate; no search-volume or future-traffic claim is made.
댓글
댓글 쓰기
안녕하세요 :)