RecurrentEdgeProcessStorageNeed

Params

name

A human readable description of the object.

edge_component

An instance of EdgeStorage.

Backwards links

• RecurrentEdgeProcess

Calculated attributes

recurrent_need

Example value: 168 values in kB:
first 10 vals [200, 200, 200, 200, 200, 200, 200, 200, 200, 200],
last 10 vals [200, 200, 200, 200, 200, 200, 200, 200, 200, 200]

Depends directly on:

• Recurrent storage needed for edge process

through the following calculations:

You can also visit the link to edge process storage need recurrent need’s full calculation graph.

recurrent_need_validation

Example value: 168 values in kB:
first 10 vals [200, 200, 200, 200, 200, 200, 200, 200, 200, 200],
last 10 vals [200, 200, 200, 200, 200, 200, 200, 200, 200, 200]

Depends directly on:

• edge process storage need recurrent need

through the following calculations:

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

unitary_hourly_need_per_usage_pattern

Dictionary with EdgeUsagePattern as keys and Edge process storage need unitary hourly need for default edge usage pattern as values, in kilobyte.

Example value: {
EdgeUsagePattern Default edge usage pattern (f80985): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in kB:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
last 10 vals [200, 200, 200, 200, 200, 200, 200, 200, 200, 200],
}

Depends directly on:

• edge process storage need recurrent need
• edge usage journey hourly nb of edge usage journeys in parallel
• devices country timezone from user data

through the following calculations:

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

cumulative_unitary_storage_need_per_usage_pattern

Dictionary with EdgeUsagePattern as keys and Edge process storage need cumulative unitary storage need for default edge usage pattern as values, in terabyte_stored.

Example value: {
EdgeUsagePattern Default edge usage pattern (f80985): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in GB_stored:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
last 10 vals [21, 21, 21, 21, 21, 21, 21, 21, 21, 21],
}

Depends directly on:

• edge process storage need unitary hourly need for Default edge usage pattern

through the following calculations:

You can also visit the link to edge process storage need cumulative unitary storage need for Default edge usage pattern’s full calculation graph.

total_hourly_need_across_usage_patterns

Edge process storage need total hourly need across usage patterns in concurrent * terabyte_stored.

Example value: 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in ·TB_stored:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
last 10 vals [105, 105, 105, 105, 105, 83.9, 62.9, 41.9, 20.9, 0]

Depends directly on:

• edge process storage need cumulative unitary storage need for Default edge usage pattern
• edge usage journey hourly nb of edge usage journeys in parallel

through the following calculations:

You can also visit the link to edge process storage need total hourly need across usage patterns’s full calculation graph.

fabrication_impact_repartition_weights

Dictionary with RecurrentEdgeProcess as keys and Edge process weight in edge process storage need impact repartition as values, in concurrent.

Example value: {
RecurrentEdgeProcess edge process (75032e): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in M:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0.000999, 0.002, 0.003],
last 10 vals [0.005, 0.005, 0.005, 0.005, 0.005, 0.004, 0.003, 0.002, 0.000997, 0],
}

Depends directly on:

• edge function weight in edge process impact repartition

through the following calculations:

You can also visit the link to edge process weight in edge process storage need impact repartition’s full calculation graph.

fabrication_impact_repartition_weight_sum

Sum of edge process storage need fabrication impact repartition weights in concurrent.

Example value: 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in M:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 0.000999, 0.002, 0.003],
last 10 vals [0.005, 0.005, 0.005, 0.005, 0.005, 0.004, 0.003, 0.002, 0.000997, 0]

Depends directly on:

• edge process weight in edge process storage need impact repartition

through the following calculations:

You can also visit the link to Sum of edge process storage need fabrication impact repartition weights’s full calculation graph.

fabrication_impact_repartition

Dictionary with RecurrentEdgeProcess as keys and Edge process storage need fabrication impact attribution to edge process as values, in concurrent.

Example value: {
RecurrentEdgeProcess edge process (75032e): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in :
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
}

Depends directly on:

• edge process weight in edge process storage need impact repartition
• Sum of edge process storage need fabrication impact repartition weights

through the following calculations:

You can also visit the link to edge process storage need fabrication impact attribution to edge process’s full calculation graph.

usage_impact_repartition_weights

Dictionary with RecurrentEdgeProcess as keys and Edge process weight in edge process storage need impact repartition as values, in concurrent * gram / kilowatt_hour.

Example value: {
RecurrentEdgeProcess edge process (75032e): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in ·g/kWh:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 84900, 170000, 255000],
last 10 vals [425000, 425000, 425000, 425000, 425000, 340000, 255000, 170000, 84700, 0],
}

Depends directly on:

• edge function weight in edge process impact repartition

through the following calculations:

You can also visit the link to edge process weight in edge process storage need impact repartition’s full calculation graph.

usage_impact_repartition_weight_sum

Sum of edge process storage need usage impact repartition weights in concurrent * gram / kilowatt_hour.

Example value: 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in ·g/kWh:
first 10 vals [0, 0, 0, 0, 0, 0, 0, 84900, 170000, 255000],
last 10 vals [425000, 425000, 425000, 425000, 425000, 340000, 255000, 170000, 84700, 0]

Depends directly on:

• edge process weight in edge process storage need impact repartition

through the following calculations:

You can also visit the link to Sum of edge process storage need usage impact repartition weights’s full calculation graph.

usage_impact_repartition

Dictionary with RecurrentEdgeProcess as keys and Edge process storage need usage impact attribution to edge process as values, in concurrent.

Example value: {
RecurrentEdgeProcess edge process (75032e): 105192 values from 2025-01-01 00:00:00+00:00 to 2037-01-01 00:00:00+00:00 in :
first 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
last 10 vals [1, 1, 1, 1, 1, 1, 1, 1, 1, 1],
}

Depends directly on:

• edge process weight in edge process storage need impact repartition
• Sum of edge process storage need usage impact repartition weights

through the following calculations:

You can also visit the link to edge process storage need usage impact attribution to edge process’s full calculation graph.