DataMovementEnergyScenario
Sustainability scenarios · Implementation: mlsysim/engine/scenario_definitions/sustainability.py.
Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.
One weight of bytes_per_param used for flops_per_param FLOPs at stated per-op energies.
Notes
Equation: The result property composes mlsysim.solvers.DataMovementEnergyModel.solve with the stored fields and any derived properties described below.
Assumptions: Inputs use the units and validity ranges of mlsysim.solvers.DataMovementEnergyModel.solve. The named scenario supplies a fixed configuration rather than observations of a new run.
Excludes: Additional runtime effects or statistical guarantees beyond the cited solver contracts; no measurement is performed by this wrapper.
References
Derivation: The result property composes mlsysim.solvers.DataMovementEnergyModel.solve with the stored fields and any derived properties described below. Individual property contracts identify the exact accounting expression or reusable calculation. Registry entries supply the scenario inputs; this class does not turn them into measured outcomes.
Examples
Evaluate a named scenario using its declared inputs.
>>> from mlsysim import Scenarios
>>> scenario = Scenarios.BatchOneDecodeWeightEnergy
>>> round(float(scenario.result.compute_energy.magnitude), 4)
20.0Attributes
| Name | Description |
|---|---|
| bytes_per_param | |
| energy_per_byte | |
| energy_per_flop | |
| flops_per_param | |
| operand_bytes | |
| result | Return the modeled DataMovementEnergy result from |
energy_per_flop
Type: Quantity.
Declared default: required.
energy_per_byte
Type: Quantity.
Declared default: required.
flops_per_param
Type: float.
Declared default: required.
bytes_per_param
Type: Quantity.
Declared default: required.
operand_bytes
Type: Quantity.
Declared default: required.
result
engine.scenario_types.DataMovementEnergyScenario.result
Return the modeled DataMovementEnergy result from mlsysim.solvers.DataMovementEnergyModel.solve.
Equation: the scenario supplies its named fields to that solver. Returned quantity units, validity conditions, and omissions follow its calculation contract; this property adds no empirical calibration.