>
PVU, RVU and VPC

How PVU Is Calculated on a 32 Core Host

IBM Audit Journal · PVU, RVU and VPC Metrics · May 2026

PVU is a core based metric: the PVU rating per core multiplied by the number of cores the IBM software can use. A 32 core host is the cleanest way to see the gap between full-capacity and sub-capacity, because the same workload can cost eight times as much depending on whether your ILMT evidence holds.

The PVU formula

PVU equals the PVU rating per core multiplied by the cores allocated to the IBM software. The per core rating is not a single number; it comes from the IBM PVU table and depends on the processor brand, model and generation. Many common Intel server cores are rated at 70 PVU, while other processors carry higher ratings.

A worked example on a 32 core host

Take a host with 32 physical cores running a single eligible IBM product, on a processor rated at 120 PVU per core. The two outcomes sit far apart:

Same host, same software, same workload. The difference between 3,840 and 480 PVU is entirely a question of which number you can prove.

Why the per core rating matters

Because the rating is read from the IBM PVU table per processor, two hosts with the same core count can carry different PVU totals. A processor rated at 70 PVU per core gives 2,240 PVU at full capacity on the same 32 cores, against 3,840 for a 120 PVU processor. Identifying the correct rating for the actual silicon is the first place reconciliations recover money.

What turns 480 into 3,840

Sub-capacity is earned, not assumed. To hold the 480 PVU position you need an approved tool deployed within 90 days, running continuously, producing quarterly reports kept for two years. Miss any one and IBM is entitled to charge the full 3,840 PVU for the affected period, even if the software never touched the other 28 cores.

How we recalculate

An independent recalculation rebuilds the number from the evidence: the processor model and its true PVU rating, the cores actually available to the product, the hypervisor caps, and the ILMT history that proves them. Where the evidence supports sub-capacity, we hold the lower figure. Where it does not, we fix the configuration before the gap becomes a settlement line.

What this means under audit

On a 32 core host the difference between a defensible sub-capacity position and a broken one is the difference between 480 PVU and 3,840 PVU for the same workload. The number IBM charges is decided not by what the software actually used, but by whether your ILMT reports prove it.

Related reading.

Recompute the PVU before IBM anchors the number.

We have defended more than $250M in IBM audit exposure across 500+ engagements, with findings reduced by 30 to 92%. Start with our PVU Reconciliation service or get help now.

Get audit help now →

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019