Mainframe Processor

IBM Telum II Processor

The mainframe processor that proved IBM's whole AI strategy. Telum II does not go in a Power server, but the AI engine inside it is the reason the Spyre card exists, and the reason IBM talks about inference in milliseconds rather than seconds.

Vendor: IBM Availability: Shipping in IBM z17. Not available for IBM Power servers. Process node: 5 nm Operating environment: IBM z17 and LinuxONE systems Deployment: Integrated mainframe processor, not orderable separately

Telum II is a mainframe chip. You will not put one in a Power server and it has nothing to do with IBM i. It is in this directory for one reason: it is where IBM's current AI hardware idea was proven, and understanding it explains why the Spyre card behaves the way it does.

The idea it proved

Banks wanted to check whether a card payment was fraudulent while the payment was still happening, not five minutes later in a batch report. That is a brutal deadline. Sending the transaction out to a separate AI server and waiting for a reply was too slow, so IBM put the AI engine on the processor itself.

It worked. Telum shipped with an on-chip AI accelerator, Telum II improved it and added a data processing unit to handle input and output, and the design became IBM's template: put the answering machine as close to the data as physically possible.

The line from here to your Power server

How one design idea reached three different IBM machines

ChipWhere it runsWhat it does for AI
Telum and Telum IIIBM Z and LinuxONEAI engine on the processor, scoring inside a live transaction
AIUIBM Research onlyScaled that engine up into a whole 32-core chip
Spyre AcceleratorIBM Power 11, IBM Z, LinuxONEThe AIU turned into a PCIe card you can order
Matrix Math AccelerationEvery Power 10 and Power 11 coreThe same close-to-the-data principle, built into the processor you already own

Different chips, one consistent argument: keep the model next to the data instead of shipping the data to the model.

Telum II is background for a Power buyer, not a purchasing option. If you are comparing mainframe and Power options in the same project, treat them as separate evaluations.