Skip to content

RecurrentEdgeProcessCPUNeed

Internal RecurrentEdgeComponentNeed created automatically by a RecurrentEdgeProcess, mirroring its compute need on the parent EdgeComputer's CPU component.

Params

name

A human readable description of the object.

edge_component

Component on the parent EdgeComputer that this need targets.

An instance of EdgeComputerCPUComponent.

Calculated attributes

recurrent_need

Recurrent compute need, copied from the parent RecurrentEdgeProcess's compute profile.

Example value: 168 values: first=1 cpu core, last=1 cpu core, mean=1 cpu core, min=1 cpu core, max=1 cpu core, std=0

Depends directly on:

through the following calculations:

You can also visit the link to Recurrent need’s full calculation graph.

recurrent_need_validation

Validates that the recurrent need uses a unit compatible with its target component, and (for workload-style needs) that values stay between 0 and 1.

Example value: 168 values: first=1 cpu core, last=1 cpu core, mean=1 cpu core, min=1 cpu core, max=1 cpu core, std=0

Depends directly on:

through the following calculations:

You can also visit the link to Validated recurrent need’s full calculation graph.

unitary_hourly_need_per_usage_pattern

Hourly resource demand for one edge device, generated by replaying the typical-week pattern across the modeling period in the country's timezone, and scaled by how often the need appears in the journey.

Example value: {
EdgeUsagePattern Default edge usage pattern (b29a7b03-dba): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00: first=1 cpu core, last=1 cpu core, mean=1 cpu core, min=1 cpu core, max=1 cpu core, std=0,
}

Depends directly on:

through the following calculations:

You can also visit the link to Unitary hourly need for Default edge usage pattern’s full calculation graph.

total_hourly_need_across_usage_patterns

Total hourly demand on the component, summed across every EdgeUsagePattern after multiplying by the hourly count of edge devices in deployment.

Example value: 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00: first=1.06 ·cpu core, last=0.607 ·cpu core, mean=10300000 ·cpu core, min=0, max=20700000 ·cpu core, std=5960000 ·cpu core

Depends directly on:

through the following calculations:

You can also visit the link to Total hourly need across usage patterns’s full calculation graph.