charles/supply
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add pareto and others

Browse Source
This commit is contained in:
charles
2026-05-19 08:38:31 -07:00
parent 7b4b2cc946
commit bc4f85518f
3 changed files with 22 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
book/ch05_virtual_resources.md
+10 -2
View File
@@ -57,8 +57,16 @@ A critical failure in this process is **Resource Stranding**. This occurs when a
MIP solvers prevent stranding by optimizing the *balance* of resources. Instead of merely packing for density, the model penalizes imbalanced remaining capacity, encouraging the placement of VMs that "complement" the existing resource footprint of the server.
### Industry Solvers
Solving these combinatorial problems at cloud scale requires high-performance solvers such as **Gurobi**, **CPLEX**, or **Google OR-Tools**, often augmented by ML-driven heuristics to provide "warm starts" for the optimization loop.
### The Optimization Frontier: Utilization vs. Isolation
The challenge of resource allocation is not merely a puzzle of "fitting" VMs into servers, but a navigation of the **Pareto Frontier**.
The fundamental trade-off exists between two competing objectives:
1. **The Provider's Goal (Max Hardware Utilization):** To minimize CAPEX and maximize profit, the provider seeks the highest possible density. This pushes the system toward "tight packing," where resources are utilized to their limit.
2. **The Customer's Goal (Performance Isolation & SLA Guarantees):** The customer seeks consistency and predictability. This requires "loose packing" or over-provisioning to ensure that a "noisy neighbor" cannot degrade their performance.
Any point on the Pareto frontier represents a specific balance of these goals. A placement strategy is Pareto optimal if you cannot increase hardware utilization without simultaneously increasing the risk of an SLA violation (or decreasing isolation).
This framework also explains **Resource Stranding**. When a system fails to reach a Pareto optimal state in its multi-dimensional resource allocation (CPU, RAM, Disk), it results in "waste"—stranded resources that cannot be utilized because a complementary resource is exhausted. In the "Atoms to Bits" transition, this is the digital equivalent of shipping a half-empty container because the remaining space is the wrong shape for any available cargo.
## Conceptual Mapping: Virtual vs. Traditional SCM