Skip to main content

ObjectStorageBillScenario

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.

A dataset kept in object storage for a billing period and read reads times across a boundary.

Notes

Equation: Compose mlsysim.solvers.ObjectStorageBillModel.

Assumptions: The stated fields are inputs to mlsysim.solvers.ObjectStorageBillModel; its documented validity regime, units, and modeling choices apply unchanged.

Excludes: This scenario adds no measurement, empirical calibration, or mechanisms beyond mlsysim.solvers.ObjectStorageBillModel.

References

Derivation: this scenario binds its input fields to the referenced implementation contracts: mlsysim.solvers.ObjectStorageBillModel. The methods below identify any additional arithmetic.

Examples

>>> from mlsysim import Scenarios
>>> case = Scenarios.ObjectStorage100TB
>>> type(case.result).__name__
'ObjectStorageBillResult'

Attributes

Name Description
billing_period
dataset_bytes
egress_rate
files
reads
request_fee
requests_per_fee
result Evaluate this scenario through mlsysim.solvers.ObjectStorageBillModel.solve.
retrieval_rate
storage_rate

dataset_bytes

Type: Quantity.

Declared default: required.

storage_rate

Type: Quantity.

Declared default: required.

billing_period

Type: Quantity.

Declared default: required.

egress_rate

Type: Quantity.

Declared default: required.

reads

Type: int.

Declared default: required.

files

Type: int.

Declared default: required.

request_fee

Type: Quantity.

Declared default: required.

requests_per_fee

Type: int.

Declared default: required.

retrieval_rate

Type: Quantity.

Declared default: required.

result

engine.scenario_types.ObjectStorageBillScenario.result

Evaluate this scenario through mlsysim.solvers.ObjectStorageBillModel.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.

Back to top