IBM Processor Value Unit (PVU) Metric

IBM Processor Value Unit (PVU) Metrics

• PVU: A metric to license software based on server processing power.
• Calculation: Determined by processor type and quantity.
• Usage: Ensures fair licensing based on actual capacity.
• Measurement: Counts the processing core for license allocation.
• Benefit: Offers cost-based licensing tied to computing resources.

What is an IBM Processor Value Unit (PVU)?

A Processor Value Unit (PVU) is a licensing metric used by IBM to determine the cost of licensing its software products. It represents a system’s processing power, which depends on hardware configuration and processor type.

Each processor core in your system is assigned a specific number of PVUs based on its capabilities, and these PVUs determine the total licensing cost for an IBM software product.

Key points about PVUs:

• PVUs vary by hardware: Different processor types are assigned different PVU values based on their power and capability.
• IBM sets PVU requirements: IBM maintains a list of PVU values for various processors to help calculate software licensing.
• PVU is per core: The value is assigned based on the number of cores, not the physical processor.

Why PVU Metrics Matter

IBM uses the PVU metric to align licensing costs with the processing power utilized. In simpler terms, it allows IBM to charge customers based on how much computational power they are using, which provides more flexibility and fairness than a flat rate.

If you miscalculate or underestimate PVU usage, you might face non-compliance penalties or unexpected licensing costs. On the other hand, overestimating your requirements can lead to unnecessary expenses. Thus, understanding and adequately calculating PVU metrics is crucial.

How PVU Values are Assigned

IBM maintains a table that assigns specific PVU values to different processors, depending on the brand and model. For example, an Intel Xeon processor may have a different PVU value than an IBM Power processor.

IBM’s PVU Table provides detailed values for a wide range of processors and is updated regularly to account for new hardware models.

Here are some common examples:

• Intel Xeon E5 Series: 70 PVUs per core
• AMD Opteron 6000 Series: 50 PVUs per core
• IBM Power7 Processor: 120 PVUs per core

IBM provides an updated PVU Table on its official website that outlines these values for all supported processors.

Calculating PVU Usage for IBM Software

To calculate your PVU usage, you need to know a few key details:

1. Processor Type and Model: The model of your processor will determine the PVU value per core.
2. Number of Processor Cores: You must determine how many cores the software uses.

The formula to calculate PVU usage is quite simple:

PVU Usage = (Number of Cores) × (PVU per Core)

Let’s go through a step-by-step example:

Example Scenario

You are using IBM WebSphere Application Server on a server with an Intel Xeon E5-2667 processor. The server has 8 cores.

1. Determine the PVU per Core: Based on IBM’s PVU Table, the Intel Xeon E5-2667 has 70 PVUs per core.
2. Number of Cores: Your server has 8 cores.
3. Calculate PVU Usage:PVU Usage = 8 cores × 70 PVUs per core = 560 PVUs

This means you need to purchase a license for 560 PVUs for your WebSphere Application Server.

Common Pitfalls and How to Avoid Them

Calculating PVU usage seems straightforward, but there are common mistakes that can lead to incorrect licensing:

• Failing to Consider Virtualization: The number of cores allocated to virtual machines in a virtual environment also impacts PVU usage. IBM requires calculating PVUs based on the virtual cores assigned to the IBM software.
• Incorrect Processor Identification: Sometimes, organizations use older or outdated PVU tables, leading to incorrect PVU calculations. Always check IBM’s latest PVU table.
• Dynamic Resource Allocation: If your environment uses dynamic resource allocation (such as cloud or hypervisors), it may change the number of cores used by a software product, affecting the PVU calculation. IBM offers a Sub-Capacity Licensing model for such environments, allowing organizations to pay based on allocated resources.

Tools to Assist with PVU Calculation

IBM provides tools to help calculate PVU usage effectively:

• IBM License Metric Tool (ILMT): IBM’s official tool helps organizations track and report on PVU consumption. ILMT automates the discovery and measurement of PVU usage, which is especially useful in complex environments.
• PVU Calculator Spreadsheet: Some organizations use spreadsheets to track PVU usage manually. IBM provides example templates that can help calculate usage step-by-step.
• IBM’s PVU Table: The official PVU table is essential for determining PVU values.

PVU Licensing in Virtual Environments

Virtualization adds a layer of complexity to PVU calculation. Understanding how many virtual cores are allocated to each IBM software product in virtual environments is important. Here’s how you can address some common scenarios:

• Dedicated Virtual Machine: If you assign a dedicated VM to run an IBM product, the number of virtual cores assigned to that VM is used to calculate PVUs. For example, if a VM with 4 virtual cores uses IBM DB2 software, and the PVU value per core is 50, the total PVUs would be 4 × 50 = 200 PVUs.
• Sub-Capacity Licensing: IBM offers sub-capacity licensing to support customers using virtualization platforms like VMware or Hyper-V. This allows you only to license your processing power, which can lead to significant cost savings.

Example

You have an IBM product on a VMware virtual machine with 6 virtual cores, each rated at 100 PVUs. The calculation would be:

PVU Usage = 6 × 100 = 600 PVUs

If you dynamically increase the number of virtual cores, you must also increase the PVU count accordingly.

Sub-Capacity vs. Full-Capacity Licensing

IBM offers two main types of PVU licensing:

1. Full-Capacity Licensing: You need to license the entire physical environment, regardless of how many cores the software actively uses. This method is simple but expensive, especially if not all cores are utilized effectively.
2. Sub-Capacity Licensing: This allows organizations to license only the resources actively used by IBM software. Sub-capacity licensing is common in virtualized environments where workloads fluctuate. To take advantage of sub-capacity licensing, you must use the IBM License Metric Tool (ILMT) and meet specific IBM requirements.

Tracking PVU Usage with ILMT

The IBM License Metric Tool (ILMT) is mandatory for any organization seeking sub-capacity licensing. ILMT helps track the PVUs consumed by your systems in real time, reducing the risk of non-compliance.

Benefits of Using ILMT:

• Automated Tracking: ILMT automates the tracking and reporting of PVU consumption.
• Detailed Reporting: It provides detailed reports that can help prove compliance in case of an audit.
• Cost Efficiency: ILMT helps you save on licensing costs by ensuring that you only pay for what you use.

PVU Licensing Compliance

Compliance is a critical aspect of managing IBM software licenses. Non-compliance with IBM’s PVU licensing can lead to significant penalties and possibly time-consuming and costly audits.

Compliance Tips:

• Use ILMT Regularly: Always use the IBM License Metric Tool to track PVU usage.
• Monitor Processor Changes: If you upgrade or change hardware, update your PVU calculations accordingly.
• Keep Detailed Records: Maintain records of all your licensing and PVU calculations to simplify the audit process.
• Stay Updated: Ensure you are always working with the latest PVU values for your processors, as IBM updates the PVU table regularly.

Summary of Key Steps to Calculating PVU Usage

1. Identify Processor Type: Refer to the IBM PVU Table to determine your processor’s PVU value per core.
2. Count Processor Cores: Identify how many physical or virtual cores the IBM software uses.
3. Multiply PVU per Core by Number of Cores: This gives you the total PVU requirement.

Common Questions About PVU Licensing

• What happens if I exceed the allocated PVU usage?
  If your usage exceeds the allocated PVUs, you must purchase additional licenses to remain compliant. IBM audits can impose penalties if the usage is higher than what you’re licensed for.
• How often should I check PVU usage?
  Ideally, PVU usage should be checked regularly, especially in dynamic environments where resource allocation changes frequently. Monthly checks can help ensure compliance.
• Can I mix sub-capacity and full-capacity licenses?
  It is possible, but careful tracking is required to ensure compliance. Using ILMT helps manage such mixed environments.

FAQs: Understanding Processor Value Unit (PVU) Metrics

What is a Processor Value Unit (PVU)?
A PVU is a unit measuring processing power for software licensing on servers.

How is the PVU metric calculated?
PVU calculations depend on both the processor type and the number of cores.

Why are PVU metrics used?
They help align software licensing costs with actual server usage.

Can PVU counts vary between servers?
Yes, PVU counts depend on the processor model and server configuration.

What is the purpose of PVU licensing?
To match license costs with the processing power used.

Is there a difference between PVU and core-based licensing?
PVU considers cores and processor models, while core-based counts cores only.

How do I calculate the required PVU?
Refer to the PVU table provided by the software vendor for core-based values.

Are PVU requirements the same for all software?
No, each software vendor may have unique PVU requirements.

What is the impact of adding processors on PVUs?
Adding processors increases the PVU count, affecting licensing costs.

How often should PVU calculations be updated?
Whenever you modify or expand server hardware to ensure licensing compliance.

Does PVU apply to virtualized environments?
Yes, PVU counts apply based on assigned virtual processing power.

Is PVU-based licensing flexible for cloud servers?
It can be used for cloud servers, but specifics vary by vendor.

What are the benefits of PVU over traditional licensing?
PVU licensing is aligned with the actual hardware capacity, offering fair costs.

How can I track PVU requirements?
Use vendor-provided tools to measure and monitor PVU usage.

Are there any discounts available for PVU licenses?
Some vendors offer volume discounts or bundling options for PVU-based licenses.