Usage metering

Measure infrastructure where the work actually happens.

Hyjal’s unit of infrastructure is execution—not a reserved worker waiting for a request.

Consumption follows the execution window.

The runtime lifecycle gives every request a clear beginning and end.

Before
No active work
There is no request-specific execution to meter.
Start
Request enters
Afterburner creates a fresh instance for the work.
Run
Execution is measured
The platform observes the work while the instance is active.
End
Request completes
The instance is discarded and the execution window closes.

The meter follows the work from entry to completion instead of following an always-on machine.

A bounded lifecycle creates a more legible relationship between application activity and infrastructure consumption.

OpenWork begins

A request creates the need for execution.

Start

ActiveWork is measured

Runtime activity exists only while the request is being served.

Run

ClosedWork ends

Completion closes the instance and its metering boundary.

Stop

Usage begins with work. It ends with work.

Start building, or review the workload’s execution profile with the Hyjal team.