A PVU, or Processor Value Unit, is IBM's per-core licensing metric in which the required quantity equals the number of activated cores multiplied by a processor-specific rating of 50, 70, or 100 PVUs per core drawn from IBM's PVU table, so a 16-core server on a 70-PVU processor requires 1,120 PVUs of license for each PVU-metered product it runs. The metric prices a large share of IBM middleware, from WebSphere to MQ to Db2, and the PVU rating of the underlying chip can swing the bill by a factor of two for identical core counts.
The PVU calculation
The formula is deliberately simple: activated cores times the PVU rating for that processor type equals required PVUs. IBM publishes the rating per processor family, and it does not track raw clock speed, so two servers with the same core count can carry different PVU bills depending on the chip.
| Processor type | PVU per core | 16-core server PVUs |
|---|---|---|
| Most x86 (Intel, AMD), per core | 70 | 1,120 |
| High-end x86 (large socket counts) | 100 | 1,600 |
| IBM Power (selected models) | 100 | 1,600 |
| Entry-class processors | 50 | 800 |
Per-PVU list pricing varies by product. As an illustration, a product listed near $55 per PVU on a 1,120-PVU server lists at roughly $61,600 before discount. The same workload on a 100-PVU-per-core chip would list near $88,000, a 43 percent swing driven purely by the processor rating. The way these PVU counts roll into product pricing is detailed in IBM PVU licensing.
Sub-capacity caps the PVU count
Left unmanaged, PVU licensing counts every activated core on the physical host. Sub-capacity licensing instead counts only the cores allocated to the virtual machine running the IBM product, but only if the measurement is proven with the IBM License Metric Tool.
Compliance warning: The PVU saving from virtualization exists only on paper until ILMT proves it. A four-vCPU WebSphere instance on a 64-core, 70-PVU host should license 280 PVUs under sub-capacity, against 4,480 PVUs at full capacity, a sixteen-fold difference. Without a correctly configured ILMT report, IBM is contractually entitled to bill the full 4,480. The PVU metric is only as cheap as the sub-capacity evidence behind it.
Why it matters to buyers
PVU is the metric where hardware decisions become licensing decisions, because the processor rating and the core count together set the bill before any discount applies. A buyer choosing servers without checking the PVU table can double an IBM liability with a chip selection that looks identical on a spec sheet. The disciplined approach is to model PVU exposure during hardware refresh, deploy on lower-rated processors where the IBM footprint is heavy, and prove every sub-capacity claim with ILMT. Our IBM advisory practice models PVU exposure before purchase, and the full metric context sits in the IBM licensing complete guide alongside sub-capacity licensing.
Which IBM products use the PVU metric
The PVU metric covers a broad slice of IBM middleware rather than the entire catalog, which is why identifying the metric behind each product is the first step in any IBM cost model. WebSphere Application Server, MQ, Db2, and many of the analytics and integration products are licensed by PVU, while other products use authorized user, resource value unit, or virtual processor core metrics instead. A single estate commonly mixes several metrics, so a server can carry a PVU obligation for one product and a user obligation for another running beside it. The consequence is that PVU exposure must be calculated product by product, with each product mapped to its metric before the core count and processor rating are applied. Misreading the metric, for example assuming a product is PVU-based when it has moved to virtual processor core licensing, produces a count that is wrong before any measurement begins. The product-to-metric mapping is maintained in IBM's licensing documentation and is one of the items validated at the start of an IBM review, because every downstream number depends on it being correct.
Why IBM uses the PVU metric
The PVU metric exists to price software against the computing power of the hardware it runs on rather than a flat per-server fee, so a product on a large, powerful processor costs more to license than the same product on a modest one. The processor-specific rating is IBM's way of approximating that capacity difference without measuring raw performance directly. For buyers, the practical effect is that the licensing bill is decided partly by procurement and infrastructure teams choosing hardware, not only by the software owner. That makes PVU a metric where cross-team coordination pays off: aligning processor selection with the IBM software footprint, before servers are bought, is the cheapest moment to control PVU cost.