UtilizationLossScenario
Data scenarios · Implementation: mlsysim/engine/scenario_definitions/data.py.
Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.
fleet’s accelerators billed at device_hour_rate while utilization falls.
Notes
Equation: Compose mlsysim.solvers.UtilizationLossModel.
Assumptions: The stated fields are inputs to mlsysim.solvers.UtilizationLossModel; its documented validity regime, units, and modeling choices apply unchanged.
Excludes: This scenario adds no measurement, empirical calibration, or mechanisms beyond mlsysim.solvers.UtilizationLossModel.
References
Derivation: this scenario binds its input fields to the referenced implementation contracts: mlsysim.solvers.UtilizationLossModel. The methods below identify any additional arithmetic.
Examples
>>> from mlsysim import Scenarios
>>> case = Scenarios.InputStallIdleCost1K
>>> type(case.result).__name__
'UtilizationLossResult'Attributes
| Name | Description |
|---|---|
| degraded_utilization | |
| device_hour_rate | |
| duration | |
| fleet | |
| healthy_utilization | |
| result | Evaluate this scenario through mlsysim.solvers.UtilizationLossModel.solve. Equation: |
fleet
Type: Fleet.
Declared default: required.
device_hour_rate
Type: Quantity.
Declared default: required.
healthy_utilization
Type: float.
Declared default: required.
degraded_utilization
Type: float.
Declared default: required.
duration
Type: Quantity.
Declared default: required.
result
engine.scenario_types.UtilizationLossScenario.result
Evaluate this scenario through mlsysim.solvers.UtilizationLossModel.solve. Equation: pass the stated fields to that implementation; its contract defines the calculation and feasibility tests. Units: each returned field follows the referenced result schema; no independent equation is evaluated by this wrapper.