Genesis had the faster clock; Super NES had twice the work RAM
Nintendo and Sega assigned graphics and sound to dedicated hardware, while Star Fox put an extra processor in the cartridge itself.

The Genesis wins if the contest ends at the CPU clock. The Super NES wins if it ends at main work memory. The schoolyard console argument managed to pick a benchmark before anybody had a benchmark.
Sega’s developer documentation gives the NTSC main CPU clock as 7.67 MHz, with PAL at 7.60 MHz. Its Motorola 68000 has 64 KB of main RAM. A separate Z80 handles the sound hardware and has 8 KB of dedicated RAM. The main processor has colleagues; counting only its clock leaves their work out of the conversation.
The graphics processor has its own 64 KB of video RAM. Sega describes two scrolling playfields and a sprite plane, with up to 80 sprites defined and 20 displayed on a scanline. Those are practical limits a game has to fit, even if the CPU still has time to spare. A faster cashier doesn’t help when all the shelves are full.
Nintendo’s specifications preserved by SNES Central label the larger memory pool “CPU temp. storage.” That 128 KB belongs in the work-memory comparison. Its 64 KB of video RAM belongs in a different row, where the two machines match.
Nintendo lists three clock rates, 3.58, 2.68 and 1.79 MHz. Treating the highest one as an all-purpose operating speed gives the Super NES a tidier spec sheet than its documentation does. The preserved specifications also list 128 sprites per screen and 32 per line, plus eight sound channels. The graphics and audio hardware deserve a vote in this argument.
| Resource | Genesis, NTSC | Super NES |
|---|---|---|
| Main CPU | Motorola 68000 | Custom 65C816 |
| Main CPU clock figure | 7.67 MHz | Up to 3.58 MHz |
| Main work RAM | 64 KB | 128 KB |
| Video RAM, kept separate | 64 KB | 64 KB |
Using the rounded clock figures gives 7.67 ÷ 3.58 ≈ 2.14. Work memory gives 128 ÷ 64 = 2. Neither calculation measures how quickly two different processors finish the same game logic. A tick tells us time has passed; it doesn’t say how much useful work got done.
A cartridge can complicate the comparison further. In Nintendo’s own Star Fox developer interview, Shigeru Miyamoto explains that drawing objects from many different angles for Pilotwings and F-Zero felt wasteful. He wanted to build an object once and rotate it in real time. Nintendo and Argonaut began discussing a chip, and Star Fox grew out of that work.
That chip was the Super FX, inside the game cartridge. Nintendo’s interview identifies it as the hardware that made the polygons possible. The shape of the Arwing followed the constraint too: the team could display only simple shapes, and Dylan Cuthbert says, “The only choice was a triangular shape.” A ship you remember was partly a hardware budget you could see.
A retro purchase starts with the games you want to play and their specific versions. A homebrew project needs the display limits beside the CPU and memory figures before choosing a target. The extra RAM may solve a real problem; so may a different graphics feature. Neither helps much if the game you want lives on the other machine.
Miyamoto’s request began with a development chore: drawing the same object from all those different angles. The extra processor inside Star Fox answered that problem, which neither console’s main-clock figure describes.