What this comparison shows

PlayStation 2 to H100

One comparison in this view is exactly 70×. The PlayStation 2 Graphics Synthesizer’s embedded DRAM is rated at 48 GB/s, and the H100 SXM module’s HBM3 is rated at 3.35 TB/s. Both are memory-bandwidth figures at memory scope, obtained by the theoretical-peak method. The approved derived claim divides the latter by the former and rounds to the two significant digits supported by the inputs.

The 70× ratio covers peak transfer rates between each memory and its processing units. It does not measure console performance against accelerator performance. The Graphics Synthesizer’s 48 GB/s is a maximum across separate frame-buffer, Z-buffer, and texture ports; one operation uses only part of it. The H100 is an accelerator that receives work from a host. Both caveats remain attached to the figures behind the ratio.

Other rows are independent of the 70× result. The PlayStation 2’s 32 MiB main RDRAM and the H100’s 80 GiB module memory answer different system questions, and their floating-point rates describe different processors and workloads. The page shows those figures when the catalog has them, but it does not combine them into a measure of graphics, gaming, or general-purpose performance.

At a glance

This card lists what each record states. These are the six questions every machine in the catalog is asked. A row with answers from different methods has no bar or multiplier; the line beneath it explains the difference.

QuestionSony PlayStation 2Sony Computer EntertainmentConsole · 2000Retail consoleNVIDIA H100 Tensor Core GPU (SXM)NVIDIAAccelerator · 2022SXM module
CPU clockSony PlayStation 2 (Retail console)294.912 MHzConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)not applicableno cpu component is fitted to this record
GPU clockSony PlayStation 2 (Retail console)150 MHzConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)unknownNVIDIA’s specification table for this accelerator gives floating-point rates at four precisions, a memory bandwidth and a power figure, and no clock at all.
Memory capacitylog scaleSony PlayStation 2 (Retail console)32 MiBConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)80 GiBNVIDIA H100 (SXM) GPU memoryConfirmed
Where these sit among 68 machines recorded this way
  1. 32 MiBNVIDIA GeForce 256
  2. 32 MiBSony PlayStation 2
  3. 41 943 040 BNintendo GameCube
  4. 32 GiBNVIDIA GeForce RTX 5090
  5. 80 GiBNVIDIA H100 Tensor Core GPU (SXM)
  • Sony PlayStation 2 — 28th-lowest of the 68 figures recorded this way, and 2nd-lowest of the 9 from 1997–2003.
  • NVIDIA H100 Tensor Core GPU (SXM) — the highest of the 68 figures recorded this way, and the highest of the 16 from 2019–2025.

Positions on a logarithmic scale. See all 68 over time.

Memory bandwidthSony PlayStation 2 (Retail console)48 GB/sGraphics Synthesizer embedded DRAMConfirmed3.2 GB/sPlayStation 2 main memory (Direct RDRAM)Confirmed3.2 GB/sConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)3.35 TB/sNVIDIA H100 (SXM) GPU memoryConfirmed3.35 TB/sConfirmed

These figures describe different parts of a machine (the memory and the whole machine). The figures are shown separately, and no bar is drawn. See how they are accounted for.

Peak FP32Sony PlayStation 2 (Retail console)6.2 GFLOP/sEmotion EngineConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)67 TFLOP/sNVIDIA H100 (SXM)Confirmed

These figures describe different parts of a machine (the processor and the graphics processor). The figures are shown separately, and no bar is drawn. See how they are accounted for.

PowerSony PlayStation 2 (Retail console)79 WConfirmedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)700 WNVIDIA H100 (SXM)Confirmed

These figures describe different parts of a machine (the whole machine and the graphics processor). The figures are shown separately, and no bar is drawn.

Sony PlayStation 2 (Retail console), the first record, is the multiplier baseline. Each section covers its own metrics. This comparison has no overall score. Bars are drawn to scale within a row and carry no number of their own.

Processing

Instruction rates, floating-point peaks, benchmark results and clocks. None of these converts into another.

Clock frequencycpu

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Nominal clockSony PlayStation 2 (Retail console)294.912 MHzConfirmed
baselinecaveat
Recorded as
  • Vendor-rated. Stated by the vendor.
Caveat
Sony first published this clock as "300 MHz" a year before launch and as 294.912 MHz afterwards; see the conflict ledger. The figure also covers only the CPU: geometry runs on the two vector units and drawing on a separate chip with a clock of its own.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)not recorded

Peak FP32 ratecpu

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Theoretical peakSony PlayStation 2 (Retail console)6.2 GFLOP/sConfirmed
baselinecaveat
Recorded as
  • Emotion Engine: Vendor-rated. Stated by the vendor.
Caveat
Sony states the rate without an operation mix, a precision or a benchmark, so it is a vendor peak rather than an achieved result. It is not comparable with the Dreamcast's floating-point figure, which Sega derived from a specific matrix-multiplication workload.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)not recorded

Graphics

Figures recorded against a graphics processor.

Clock frequencygpu

Both records address this quantity, but neither states a value. The figures are recorded as an explicit absence, so there is nothing to compare.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Nominal clockSony PlayStation 2 (Retail console)150 MHzConfirmed
baselinecaveat
Recorded as
  • Vendor-rated. Stated by the vendor.
Caveat
Sony states 150 MHz and derives the chip's own bandwidth figures from it, so the two agree; accounts outside Sony's documentation frequently give 147.456 MHz instead. No source cited here states that value, so it is not recorded.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)unknownNVIDIA’s specification table for this accelerator gives floating-point rates at four precisions, a memory bandwidth and a power figure, and no clock at all.
no value herecaveat
Recorded as
  • Stated by the vendor.
Caveat
Unknown rather than not-applicable, and worth noticing beside the two consumer cards in this catalog: the GeForce GTX 1080 is specified with a base clock and a boost clock, while the data-center part from the same maker is specified with neither. What NVIDIA sells here is throughput, and the frequency that produces it is left inside the figures.
Multiplier
No multiplier: no value is recorded here.
Sources

Peak FP32 rategpu

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Theoretical peakSony PlayStation 2 (Retail console)not recordedNVIDIA H100 Tensor Core GPU (SXM) (SXM module)67 TFLOP/sConfirmed
baseline states nonecaveat
Recorded as
  • NVIDIA H100 (SXM): Vendor-rated. Stated by the vendor.
Caveat
Equal to this chip's double-precision tensor-core rate, which is a coincidence of two different units and not a statement that precision costs nothing here: on the general units, single precision is twice as fast as double.
Multiplier
No multiplier: Sony PlayStation 2 (Retail console) records no value here, so there is nothing to divide by.
Sources

Memory

Capacity, bandwidth, bus width and timing. Binary and decimal prefixes are kept as the source wrote them.

Memory capacityVideo memory · memory

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Design capacitySony PlayStation 2 (Retail console)4 MiBConfirmed
baselinecaveat
Recorded as
  • Graphics Synthesizer embedded DRAM: Vendor-rated. Stated by the vendor.
Caveat
The release writes "4MB", meaning 4 MiB. The figure is quoted from the 2003 description of the merged Emotion Engine and Graphics Synthesizer chip; the embedded memory was not resized when the two dies were combined.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)built differentlyStated for the whole machine, in another row here.

Memory capacitySystem memory · memory

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Design capacitySony PlayStation 2 (Retail console)32 MiBConfirmed
baselinecaveat
Recorded as
  • PlayStation 2 main memory (Direct RDRAM): Vendor-rated. Stated by the vendor.
Caveat
The release writes "32 MB", meaning 32 MiB. The Graphics Synthesizer's 4 MiB is separate and unreachable from here, so the two are never added.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)built differentlyStated for the whole machine, in another row here.

Memory capacitywhole-system

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Design capacitylog scaleSony PlayStation 2 (Retail console)32 MiBConfirmed
baselinecaveat
Recorded as
  • Derived. Computed here from figures the vendor stated.
Caveat
Adds 1 memory-capacity figure obtained by design-capacity. Left out: 4 MiB embedded in the Graphics Synthesizer (on the drawing chip’s own die and unreachable from the processor). A total is only as trustworthy as the decision about what belongs in it, so both the terms and the exclusions are named records.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)80 GiBConfirmed
2600×the baselinecaveat
Recorded as
  • NVIDIA H100 (SXM) GPU memory: Vendor-rated. Stated by the vendor.
Caveat
NVIDIA writes "80GB", read as 80 GiB in the binary convention this catalog applies to every memory capacity. Recorded at whole-system scope because it is all the memory this device has, but it answers a narrower question than a computer's: work has to be copied here from a host before the accelerator can touch it.
Multiplier
a ÷ b (ratio v1, to 2 significant digits)
  • NVIDIA H100 Tensor Core GPU (SXM): 80 GiB
  • Sony PlayStation 2: 32 MiB
Compares memory-capacity at whole-system scope, obtained by design-capacity. Valid only within this comparability group, and reported to 2 significant digits — the precision of the least precise input.
Sources

Memory bandwidthVideo memory · memory

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Theoretical peakSony PlayStation 2 (Retail console)48 GB/sConfirmed
baselinecaveat
Recorded as
  • Graphics Synthesizer embedded DRAM: Theoretical. Stated by the vendor.
Caveat
A bus maximum. The 2560 bit are not one bus but three ports — separate read and write paths for the frame and Z buffers plus a texture path — so no single operation can consume the whole figure.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)3.35 TB/sConfirmed
70×the baselinecaveat
Recorded as
  • NVIDIA H100 (SXM) GPU memory: Theoretical. Stated by the vendor.
Caveat
A bus maximum like every other bandwidth figure here, and directly comparable with them: same metric, same scope, same method. That makes it the one place in this record where a multiplier across the whole span of the catalog is legitimate.
Multiplier
a ÷ b (ratio v1, to 2 significant digits)
  • NVIDIA H100 Tensor Core GPU (SXM): 3.35 TB/s
  • Sony PlayStation 2: 48 GB/s
Compares memory-bandwidth at memory scope, obtained by theoretical-peak. Valid only within this comparability group, and reported to 2 significant digits — the precision of the least precise input. At least one input is a theoretical peak, which is an upper bound rather than an achieved result.
Sources

Memory bandwidthSystem memory · memory

Only one of these records states this figure in this form, so there is nothing here to compare it with.

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Theoretical peakSony PlayStation 2 (Retail console)3.2 GB/sConfirmed
baselinecaveat
Recorded as
  • PlayStation 2 main memory (Direct RDRAM): Theoretical. Stated by the vendor.
Caveat
A bus maximum, not a rate any workload sustains. Rambus reaches it with a narrow channel at a very high transfer rate, which makes it more sensitive to access pattern than a wide, slow bus of the same nominal figure.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)built differentlyStated as video memory and for the whole machine, in another row here.

Memory bandwidthwhole-system

MethodSony PlayStation 2Retail consoleNVIDIA H100 Tensor Core GPU (SXM)SXM module
Theoretical peaklog scaleSony PlayStation 2 (Retail console)3.2 GB/sConfirmed
baselinecaveat
Recorded as
  • Derived. Computed here from figures the vendor stated.
Caveat
Adds 1 memory-bandwidth figure obtained by theoretical-peak. Left out: 48 GB/s inside the Graphics Synthesizer (the drawing chip’s own embedded memory, which the processor cannot read or write). A total is only as trustworthy as the decision about what belongs in it, so both the terms and the exclusions are named records.
Sources
NVIDIA H100 Tensor Core GPU (SXM) (SXM module)3.35 TB/sConfirmed
1000×the baselinecaveat
Recorded as
  • Derived. Computed here from figures the vendor stated.
Caveat
Adds 1 memory-bandwidth figure obtained by theoretical-peak. Nothing in the catalog is left out of it. A total is only as trustworthy as the decision about what belongs in it, so both the terms and the exclusions are named records.
Multiplier
a ÷ b (ratio v1, to 2 significant digits)
  • NVIDIA H100 Tensor Core GPU (SXM): 3.35 TB/s
  • Sony PlayStation 2: 3.2 GB/s
Compares memory-bandwidth at whole-system scope, obtained by theoretical-peak. Valid only within this comparability group, and reported to 2 significant digits — the precision of the least precise input.
Sources

Change it

This preset is a starting point, not a fixed set. Open it in the comparison builder to swap a record in or out. The builder needs JavaScript; this page does not.

Back to top