Dreamcast vs. PS2: 26 MB and 32 MB count different parts of the consoles
Sega’s three memory pools and Sony’s launch specification need matching labels before the division starts.
Dreamcast’s 26 MB and PlayStation 2’s 32 MB look like two numbers politely waiting to be divided. They are counting different things. This is how a console argument can become very precise while remaining wrong in the third decimal place.
Sega’s own hardware history lists Dreamcast memory as three pools: 16 MB main, 8 MB texture, and 2 MB sound. Add them and 26 MB appears. The addition works.
Sony’s September 1999 launch announcement, preserved in full by ActiveXbox, lists 32 MB of Direct RDRAM as main memory. Its graphics and sound entries appear separately. Comparing that 32 MB figure with Sega’s combined total puts one console’s whole assortment beside one selected part of the other.
| Published memory pool | Dreamcast | PlayStation 2 |
|---|---|---|
| Main memory | 16 MB | 32 MB |
| Texture / graphics entry | 8 MB texture memory | 4 MB embedded graphics VRAM |
| Sound memory | 2 MB | 2 MB |
| I/O processor memory | No separate figure in Sega’s table | 2 MB |
The graphics row keeps the manufacturers’ labels because the architectures differ. A column of megabytes can tempt a writer into treating each pool as an interchangeable bucket. A quantity reserved for one subsystem is not automatically spare room available to every other subsystem.
For main memory, 32 divided by 16 is exactly two. That statement is both useful and pleasantly unexciting. It says how the capacities compare under a matching label. It doesn’t say a game runs twice as fast, doubles its visible detail, or loads in half the time. Those would require observations of particular games doing particular work.
The sound entries also illustrate why context belongs beside a number. Both list 2 MB, yet that shared capacity doesn’t establish identical audio behavior. A memory amount leaves questions about the processing and use of that memory. Matching one ingredient does not make two recipes taste the same.
For someone choosing a console to revisit, the library and actual game remain a better starting point than a capacity trophy. A Dreamcast console or a PlayStation 2 console needs the right condition and accessories for the games someone actually intends to play. Arithmetic supplies neither a working controller nor a favorite title.
The same category mistake is easy to carry into current hardware. A combined memory total, dedicated graphics memory, and ordinary system memory can all appear on adjacent product pages. Before calculating a ratio, the comparison needs to establish which jobs each capacity covers and whether the quantities overlap.
None of that diminishes the interest of the old machines. It gives their differences somewhere more honest to live than one unlabeled number. The spec sheets settle the capacity labels. What a particular game does with those resources remains a job for the game, its designers, and a comparison that actually runs it.