Integrated Performance Score (IPS)

• Integrated Performance Score (IPS) is a target-based metric that aggregates normalized resource utilizations (CPU, memory, I/O, etc.) to assess a machine's overall health.
• It employs nonlinear mappings like tanh and exponential decay to quantify deviations from ideal targets, facilitating balanced resource management.
• The framework uses customizable weights, tolerances, and penalty terms to support precise capacity planning and effective VM right-sizing in cloud environments.

Searching arXiv for the specified paper and closely related context. The Integrated Performance Score (IPS), as instantiated by the WISE framework (“Workload/Machine Index Score”), is a single-value fitness indicator for a given workload–machine combination. Its purpose is to answer whether CPU, memory, I/O, and related resources are running too low, too high, or “just right,” how far each resource’s utilization deviates from its pre-defined ideal target, and what the aggregated health of the machine is under the workload. By mapping each resource’s utilization to a normalized score, applying weights, and penalizing any extreme over-utilization, IPS provides a rapid, tunable guide for capacity planning, right-sizing VMs, and automated instance selection (Luciano et al., 2020).

1. Definition and operational objective

IPS is defined as a single-score summary of the fitness of a computing machine under a specified workload configuration. In the WISE formulation, the score is explicitly target-based rather than purely utilization-based: it evaluates how far machine resources are operating from target levels and whether those resources are being stressed or sitting idle wasting precious resources.

The framework is designed to encompass any number of computing resources. The examples and notation include CPU, memory, disk I/O, and network, but the formulation is not limited to those resources. The central operational question is not merely whether a machine is busy, but whether the observed resource profile is balanced relative to pre-defined ideal targets and upper safety limits.

This target-centered design gives IPS a dual role. First, it is an aggregate health measure for a workload–machine combination. Second, it functions as a decision aid for resource allocation, because it distinguishes between under-utilization, over-utilization, and near-target operation. A plausible implication is that IPS is intended for comparative evaluation across machine instances only after the target, tolerance, weighting, and penalty definitions have been fixed for the workload of interest.

2. Mathematical structure

The WISE instantiation of IPS introduces the following notation (Luciano et al., 2020):

Symbol	Meaning
$n$	number of monitored resources
$u_i$	actual utilization rate of resource $i$
$t_i$	target (ideal) utilization for resource $i$
$\sigma_i$	acceptable deviation (tolerance) around $t_i$
$r^{\max}_i$	maximum safe utilization for resource $i$
$w_i \ge 0$	relative importance weight of resource $u_i$0
$u_i$1	penalty-scaling factor

The first step is a standardized deviation from target:

$u_i$2

A simple distance function is

$u_i$3

though WISE also uses nonlinear mappings of $u_i$4.

A binary penalty is imposed if a resource exceeds its maximum safe level:

$u_i$5

At the resource level, WISE specifies two common normalized mappings. The hyperbolic-tangent variant has range $u_i$6 to $u_i$7:

$u_i$8

Its interpretation is sign-sensitive: $u_i$9 indicates under-utilized, $i$0 indicates over-utilized, and $i$1 indicates on target. The exponential-decay variant has range $i$2 to $i$3:

$i$4

Its interpretation is target-proximity: $i$5 indicates exactly on target, while $i$6 indicates far from target.

The integrated score admits four variants by combining either mapping with either an $i$7- or $i$8-norm aggregation. Two representative forms are:

1. Exponential + $i$9 (best-is-highest, range $t_i$0):

$t_i$1

where a value of $t_i$2 is ideal and $t_i$3 is worst.

2. Tanh + $t_i$4 (best-is-lowest, range $t_i$5):

$t_i$6

where $t_i$7 is ideal and $t_i$8 is worst.

The more general statement is

$t_i$9

where $i$0 or $i$1, as required.

3. Computation procedure

The IPS workflow is given as a seven-step algorithm for a workload and a machine instance (Luciano et al., 2020).

First, metric collection samples each resource’s utilization $i$2 over the workload run, with examples including CPU avg, p95; RAM avg, disk I/O, and network. Second, targets and limits are defined: for each resource $i$3, one sets an ideal target $i$4, a tolerance $i$5, and an upper limit $i$6 triggering hard penalty. Third, the framework computes standardized deviations as $i$7 for $i$8.

Fourth, resource scores are computed by choosing either $i$9 or $\sigma_i$0, with optional multiplication by weight $\sigma_i$1. Fifth, penalties are computed as $\sigma_i$2. Sixth, the selected aggregation formula is applied, using either the $\sigma_i$3- or $\sigma_i$4-based IPS expression together with max/min clamping. Seventh, the resulting score is interpreted relative to the corresponding best extreme.

The interpretation step is asymmetric across score families. If IPS is near its “best” extreme, namely $\sigma_i$5 for tanh-type or $\sigma_i$6 for exp-type, the machine is well-balanced. Scores beyond pre-set thresholds, exemplified by IPS $\sigma_i$7 or IPS $\sigma_i$8, signal under/over-utilization. This suggests that IPS is not a single canonical scalar in isolation; its operational meaning depends on the selected mapping, norm, and threshold policy.

4. Illustrative example

The WISE presentation includes a three-resource example with equal weights $\sigma_i$9 and no $t_i$0-scaling, $t_i$1 (Luciano et al., 2020). The parameters and observations are:

Resource	$t_i$2, $t_i$3, $t_i$4	Observed $t_i$5
CPU avg	$t_i$6, $t_i$7, N/A	$t_i$8
RAM avg	$t_i$9, $r^{\max}_i$0, $r^{\max}_i$1	$r^{\max}_i$2
Disk avg	$r^{\max}_i$3, $r^{\max}_i$4, N/A	$r^{\max}_i$5

The standardized deviations are

$r^{\max}_i$6

$r^{\max}_i$7

$r^{\max}_i$8

No resource exceeds $r^{\max}_i$9, so all $i$0.

Using the exp-variant + $i$1 aggregation,

$i$2

$i$3

$i$4

$i$5

The stated interpretation is that IPS $i$6 on $i$7 is moderately healthy but memory is somewhat over-utilized.

Using the tanh-variant + $i$8 aggregation,

$i$9

$w_i \ge 0$0

$w_i \ge 0$1

$w_i \ge 0$2

$w_i \ge 0$3

The stated interpretation is that IPS $w_i \ge 0$4 on $w_i \ge 0$5, close to ideal $w_i \ge 0$6, indicates small deviations. The example shows that the same utilization vector can yield distinct numerical semantics depending on whether the scoring family is best-is-highest or best-is-lowest.

5. Use in resource allocation and right-sizing

IPS is presented as a guide for resource allocation decisions because it links aggregate scoring to concrete resizing actions. If IPS stays within a “sweet-spot” band, exemplified by $w_i \ge 0$7 for exp-type or $w_i \ge 0$8 for tanh-type, the instance is well-balanced (Luciano et al., 2020).

Scores below the exp-type threshold or above the tanh-type threshold suggest re-sizing. The specified actions are: under-utilization implies considering downsizing to save cost, while over-utilization implies considering upsizing or adding capacity to avoid performance degradation. Per-resource $w_i \ge 0$9 diagnostics are used to pinpoint which resource drives the score.

This use of IPS is structurally different from thresholding raw utilization streams independently. Because the score is target-based and weighted, a machine can be judged suboptimal even when no single resource is near saturation, provided the overall operating point is far from the intended target profile. Conversely, the penalty term reserves special treatment for extreme over-utilization by explicitly checking $u_i$00.

A plausible implication is that IPS can support both human-in-the-loop capacity planning and automated instance selection, provided the target and tolerance definitions capture the workload’s desired operating regime.

6. Relation to conventional metrics and experimental validation

Conventional monitoring often reports raw CPU%, RAM%, or throughput in isolation. IPS offers multi-resource aggregation, target-based normalization, nonlinear mapping, and customizability (Luciano et al., 2020). More specifically, it merges CPU, memory, disk, and network into one unified “health” measure; measures deviation from an ideal operating point rather than merely “busy vs. idle”; softens the impact of extreme outliers while still flagging dangerous over-utilization via penalties; and supports per-resource weights, diverse aggregations such as avg and p95, and user-defined thresholds.

The experimental validation described for WISE uses AWS EC2 experiments with two distinct benchmarks: MongoDB as CPU-intensive and Streaming as network-intensive. In those experiments, the WISE-derived IPS was used to rank instance types. Validation against ground-truth performance metrics—latency, throughput, and cost—yielded precision of selecting truly optimal instances often 100%, recall up to 100% especially for exp + $u_i$01 variant, and rank-biased overlap greater than $u_i$02 between IPS ranking and performance-based ranking.

Those results are presented as evidence that IPS reliably identifies right-sized VMs and can drive automated instance recommendations in cloud environments. Within the WISE framework, the significance of these results lies in showing that a target-based aggregate resource score can align with workload-level performance rankings, rather than merely summarize low-level telemetry.