IBM PVU Table 2026
The IBM PVU table reading it in 2026.
The PVU table assigns a per core rating to each processor. Here is how to read it, how to count correctly, and the moves that cut your Processor Value Unit total.
The PVU table assigns a per core rating to each processor. Here is how to read it, how to count correctly, and the moves that cut your Processor Value Unit total.
The IBM PVU table assigns a per core rating to each processor type. Read it correctly and you license the right quantity. Read it wrong and you over pay or fall out of compliance.
This guide is for license managers and infrastructure teams sizing IBM software by Processor Value Unit. Read it with the IBM PVU licensing explained guide and the IBM sub capacity licensing pillar.
The PVU table looks simple. The trap is matching your exact processor model to the right rating, because a wrong rating quietly multiplies across every core you license.
A Processor Value Unit is IBM's unit of measure for processor based licensing. Each core is assigned a number of PVUs based on its processor type, and you license the total PVUs the software can run on.
PVUs let IBM price different processors at different rates. A high performance core is worth more PVUs than a modest one. The IBM Passport Advantage PVU page is the reference for the model.
Most modern x86 cores rate at 70 PVUs. Many IBM Power cores rate at 100 or 120. Older or specialty chips carry their own values, which is why the exact model matters.
The table maps a processor vendor, brand, and model to a PVU per core value. The work is matching your hardware to the exact row, not a near neighbor.
Two chips from the same family can carry different ratings. Picking the wrong row applies the wrong multiplier to every core. Confirm the processor model from system data, not from a spec sheet assumption.
IBM updates the table as new processors ship. A rating valid two years ago may not cover a current chip. Always pull the live table when you size or true up an IBM product.
Common PVU ratings and example counts
| Processor type | PVU per core | 16 core server total |
|---|---|---|
| Modern x86 | 70 | 1,120 PVUs |
| IBM Power, mid range | 100 | 1,600 PVUs |
| IBM Power, high end | 120 | 1,920 PVUs |
| Older x86 | 50 | 800 PVUs |
A wrong PVU rating does not add a little cost. It multiplies across every core, so the error scales with the estate.
Counting is cores times rating, then summed across every server where the software can run. The second half of that sentence is where full capacity counts climb.
Multiply the activated cores by the per core PVU rating for that processor. A 16 core server at 70 PVUs per core needs 1,120 PVUs. Sum that across all eligible servers for the total entitlement.
Without ILMT you license full capacity, every core in the physical server. Sub capacity licensing limits the count to the virtual cores the software uses, but only with ILMT reporting in place.
The levers are correct ratings, sub capacity, and processor choice. Each one reduces the PVU total before any price negotiation begins.
An over stated rating inflates the count and the bill. Confirming the exact model against the current table is the fastest correction, and it sometimes reveals you are licensed for more than you need.
A lower rated processor delivers more compute per PVU. Where workloads allow, choosing a chip with a favorable rating reduces the PVU total for the same capacity, a design lever often missed.
PVU stands for Processor Value Unit, IBM's per core licensing currency. Each processor type is assigned a PVU rating, and you license the total PVUs across the cores where the software can run.
Multiply the activated cores by the per core PVU rating for that processor, then sum across all eligible servers. A 16 core server rated at 70 PVUs per core requires 1,120 PVUs.
Modern x86 cores commonly rate at 70 PVUs, while IBM Power cores often rate at 100 or 120. Older and specialty processors carry their own values, so the exact model determines the rating.
Yes, IBM updates the PVU table as new processors ship. A rating valid for an older chip may not cover a current model, so always pull the live table when sizing or truing up a product.
Yes, sub capacity licensing limits the count to the virtual cores the software actually uses rather than full physical capacity. It requires the IBM License Metric Tool to be deployed and reporting.
Applying the wrong per core rating by matching a near neighbor chip instead of the exact model. The error multiplies across every core, so it scales with the estate and creates a sizable gap.
IBM PVU sub capacity rules, ILMT posture, Passport Advantage levers, and the buyer side moves across the full IBM software estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Matching the exact processor model to the right rating is dull work, and it is the difference between a clean position and a six figure gap.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
PVU counting, sub capacity rules, and Passport Advantage levers. No noise.
