Skip to content

Server

Params

name

A human readable description of the object.

server_type

description to be done

carbon_footprint_fabrication

Carbon footprint fabrication of server in kilogram.

power

Power of server in watt.

lifespan

Lifespan of server in year.

idle_power

Idle power of server in watt.

ram

Ram of server in gigabyte_ram.

compute

Nb cpu cores of server in cpu_core.

power_usage_effectiveness

Pue of server in dimensionless.

average_carbon_intensity

Average carbon intensity of server electricity in gram / kilowatt_hour.

utilization_rate

Server utilization rate in dimensionless.

base_ram_consumption

Base ram consumption of server in megabyte_ram.

base_compute_consumption

Base cpu core consumption of server in cpu_core.

storage

An instance of Storage.

fixed_nb_of_instances

User defined number of server instances. Can be an EmptyExplainableObject in which case the optimum number of instances will be computed, or an ExplainableQuantity with a dimensionless value, in which case e-footprint will raise an error if the object needs more instances than available.

Calculated attributes

hour_by_hour_ram_need

Server hour by hour ram need in gigabyte_ram.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in GB_ram:
first 10 vals [0.03, 0.1, 0.13, 0.02, 0.1, 0.08, 0.05, 0.08, 0.12, 0.08],
last 10 vals [0.03, 0.02, 0.1, 0.02, 0.15, 0.13, 0.05, 0.05, 0.02, 0.05]

Depends directly on:

through the following calculations:

You can also visit the link to server hour by hour ram need’s full calculation graph.

hour_by_hour_compute_need

Server hour by hour compute need in cpu_core.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in cpu_core:
first 10 vals [0.0, 0.01, 0.01, 0.0, 0.01, 0.01, 0.0, 0.01, 0.01, 0.01],
last 10 vals [0.0, 0.0, 0.01, 0.0, 0.01, 0.01, 0.0, 0.0, 0.0, 0.0]

Depends directly on:

through the following calculations:

You can also visit the link to server hour by hour compute need’s full calculation graph.

occupied_ram_per_instance

ExplainableQuantity in gigabyte_ram, representing the Occupied ram per server instance including services.

Example value: 2.3 gigabyte_ram

Depends directly on:

through the following calculations:

You can also visit the link to Occupied RAM per server instance including services’s full calculation graph.

occupied_compute_per_instance

ExplainableQuantity in cpu_core, representing the Occupied cpu per server instance including services.

Example value: 2.0 cpu_core

Depends directly on:

through the following calculations:

You can also visit the link to Occupied CPU per server instance including services’s full calculation graph.

available_ram_per_instance

ExplainableQuantity in gigabyte_ram, representing the Available ram per server instance.

Example value: 112.9 gigabyte_ram

Depends directly on:

through the following calculations:

You can also visit the link to Available RAM per server instance’s full calculation graph.

available_compute_per_instance

ExplainableQuantity in cpu_core, representing the Available cpu per server instance.

Example value: 19.6 cpu_core

Depends directly on:

through the following calculations:

You can also visit the link to Available CPU per server instance’s full calculation graph.

raw_nb_of_instances

Hourly raw number of server instances in concurrent.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in concurrent:
first 10 vals [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0],
last 10 vals [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]

Depends directly on:

through the following calculations:

You can also visit the link to Hourly raw number of server instances’s full calculation graph.

nb_of_instances

Hourly number of server instances in concurrent.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in concurrent:
first 10 vals [1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0],
last 10 vals [1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0]

Depends directly on:

through the following calculations:

You can also visit the link to Hourly number of server instances’s full calculation graph.

instances_fabrication_footprint

Hourly server instances fabrication footprint in kilogram.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in kg:
first 10 vals [0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01],
last 10 vals [0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01]

Depends directly on:

through the following calculations:

You can also visit the link to Hourly server instances fabrication footprint’s full calculation graph.

instances_energy

Hourly energy consumed by server instances in kilowatt_hour.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in kWh:
first 10 vals [0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06],
last 10 vals [0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06, 0.06]

Depends directly on:

through the following calculations:

You can also visit the link to Hourly energy consumed by server instances’s full calculation graph.

energy_footprint

Hourly server energy footprint in kilogram.

Example value: 26298 values from 2024-12-31 23:00:00+00:00 to 2028-01-01 17:00:00+00:00 in kg:
first 10 vals [0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01],
last 10 vals [0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01]

Depends directly on:

through the following calculations:

You can also visit the link to Hourly server energy footprint’s full calculation graph.