Gaming Server Energy Usage Logs
This dataset provides detailed, time-stamped logs of energy consumption and operational metrics across gaming servers, including power usage, performance statistics, sustainability indicators, and server status. It enables operations teams to monitor real-time efficiency, track historical trends, and support sustainability initiatives by analyzing renewable energy usage and carbon emissions. The dataset is ideal for optimizing server infrastructure, reducing costs, and improving uptime in gaming environments.
Sample rows
preview · 8 of 120 rows · all 16 columns| log_idstring | server_statusstring | cpu_utilization_percentfloat | server_namestring | server_idstring | data_center_idstring | data_center_locationstring | timestampdatetime | energy_consumed_kwhfloat | power_draw_wattsfloat | gpu_utilization_percentfloat | memory_usage_gbfloat | renewable_energy_percentfloat | carbon_emissions_kgco2efloat | uptime_secondsinteger | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LOG-0001 | active | 77.4 | Orion-Gamma | SRV-A02 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-01T08:14:23Z | 7.12 | 1245.5 | 82 | 64.2 | 94.5 | 0.39 | 7742321 | Tournament event |
| LOG-0002 | active | 65.2 | Centauri | SRV-J13 | DC-PAR-02 | Paris Cloud Facility, Paris, FR | 2024-05-01T09:47:12Z | 2.38 | 621.9 | 28.7 | 24.6 | 100 | 0 | 1849223 | Powered by 100% renewable |
| LOG-0003 | active | 92.6 | blank | SRV-T27 | DC-MEX-04 | Mexico City, MX | 2024-05-01T11:03:09Z | 13.55 | 1457.7 | 97.4 | 127.6 | 12 | 22.8 | 9912212 | Peak load |
| LOG-0004 | active | 81.5 | Pioneer-Vega | SRV-E19 | DC-JHB-11 | Johannesburg, South Africa | 2024-05-01T12:26:44Z | 8.97 | 1042.3 | 93.2 | 84.7 | 9.5 | 31.17 | 8123442 | High traffic |
| LOG-0005 | idle | 9 | Atlas | SRV-X04 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-01T13:03:19Z | 0.42 | 44.8 | 2.7 | 3.6 | 99.6 | 0.01 | 1143223 | blank |
| LOG-0006 | idle | 2.1 | Helios | SRV-H34 | DC-SYD-07 | Sydney, NSW, Australia | 2024-05-01T13:55:10Z | 0.08 | 9.3 | 0 | 2.4 | 82.7 | 0.03 | 77432 | Scheduled downtime |
| LOG-0007 | idle | 3.5 | Centauri | SRV-J13 | DC-PAR-02 | Paris Cloud Facility, Paris, FR | 2024-05-01T14:22:11Z | 0.21 | 21.9 | 1.1 | 1.9 | 100 | 0 | 1849811 | blank |
| LOG-0008 | active | 51.7 | Nova | SRV-D08 | DC-DEL-06 | Delhi, India | 2024-05-01T15:30:02Z | 5.47 | 820.6 | 19 | 32.4 | 16.2 | 5.77 | 4828222 | blank |
| LOG-0009 | active | 23.8 | Zephyr | SRV-L88 | DC-LON-05 | London, UK | 2024-05-01T16:17:58Z | 1.34 | 197.3 | 7.6 | 12.1 | 54.9 | 0.71 | 2500023 | blank |
| LOG-0010 | offline | blank | blank | SRV-Q21 | blank | Distributed Cloud | 2024-05-01T17:41:39Z | 0 | 0 | blank | blank | 100 | 0 | 0 | Server powered off |
| LOG-0011 | maintenance | 2.5 | Prometheus | SRV-S06 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-01T19:05:44Z | 0.17 | 18.1 | 0 | 1.5 | 98.8 | 0.01 | 24012 | Routine maintenance |
| LOG-0012 | offline | blank | Orion-Gamma | SRV-A02 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-01T20:29:16Z | 0 | 0 | blank | blank | 100 | 0 | 0 | Decommissioned |
| LOG-0013 | maintenance | 0 | Astra | SRV-K57 | DC-JHB-11 | Johannesburg, South Africa | 2024-05-02T07:45:21Z | 0.31 | 38.2 | 0 | 0 | 12 | 0.03 | 315 | Firmware update |
| LOG-0014 | active | 55.6 | Atlas | SRV-X04 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-02T08:34:12Z | 3.89 | 674.4 | 23.5 | 32.7 | 94.2 | 0.27 | 1147923 | blank |
| LOG-0015 | offline | blank | Nova | SRV-D08 | DC-DEL-06 | Delhi, India | 2024-05-02T09:11:05Z | 0 | 0 | blank | blank | 16.2 | 0 | 0 | Server powered off |
| LOG-0016 | offline | blank | Apollo | SRV-T27 | DC-MEX-04 | Mexico City, MX | 2024-05-02T09:57:53Z | 0 | 0 | blank | blank | 0 | 0 | 0 | Decommissioned |
| LOG-0017 | idle | 10.6 | blank | SRV-Q21 | blank | Distributed Cloud | 2024-05-02T10:41:20Z | 1.07 | 111.6 | 0 | 4.2 | 100 | 0 | 724232 | Edge compute node |
| LOG-0018 | maintenance | 0 | Prometheus | SRV-S06 | DC-SEA-01 | Seattle Data Center, WA, USA | 2024-05-02T11:19:09Z | 0.03 | 6.7 | 0 | 0 | 98.2 | 0 | 12005 | Routine maintenance |
| LOG-0019 | idle | 8 | Zephyr | SRV-L88 | DC-LON-05 | London, UK | 2024-05-02T11:56:54Z | 0.27 | 31.2 | 0 | 0.8 | 61.1 | 0.04 | 2500823 | blank |
| LOG-0020 | active | 39.3 | Gemini | SRV-M73 | DC-PAR-02 | Paris Cloud Facility, Paris, FR | 2024-05-02T12:31:31Z | 3.02 | 477.8 | 0 | 16 | 100 | 0 | 3242211 | blank |
What the 120 rows show
from the 120-row sampleActive (server status) stands out: mean cpu_
- 32.1median cpu_
utilization_ percent - 25data centers
- 0.45median energy_
consumed_ kwh - 52.0median power_
draw_ watts - 5.7median gpu_
utilization_ percent - 12.8median memory_
usage_ gb
Median 32.1, from 0.0 to 99.8.
- string 7
- integer 1
- float 7
- datetime 1
Columns
16 columns in three groups| column | type | description | example |
|---|---|---|---|
| Text 7 columns | |||
log_id | string | Unique identifier for each energy usage log entryunique | LOG-0001 |
server_id | string | Unique identifier for the gaming server | SRV-A02 |
server_name | string | Human-readable name of the gaming serveroptional | Orion-Gamma |
data_center_id | string | Identifier for the data center where the server is locatedoptional | DC-SEA-01 |
data_center_location | string | Geographical location or address of the data centeroptional | Mexico City, MX |
server_status | string | Operational status of the server at the time of loggingactive · idle · maintenance · offline · optional | active |
notes | string | Optional notes or comments about the log entry (e.g., anomalies, maintenance events)optional | Tournament event |
| Numbers 8 columns | |||
energy_consumed_kwh | float | Amount of energy consumed by the server during the logging interval, measured in kilowatt-hours (kWh)0 or more | 7.12 |
power_draw_watts | float | Instantaneous power draw of the server at the time of logging, measured in watts (W)0 or more · optional | 1245.5 |
cpu_utilization_percent | float | CPU utilization percentage of the server at the time of logging0 to 100 · optional | 77.4 |
gpu_utilization_percent | float | GPU utilization percentage of the server at the time of logging0 to 100 · optional | 82 |
memory_usage_gb | float | Amount of memory used by the server at the time of logging, measured in gigabytes (GB)0 or more · optional | 64.2 |
renewable_energy_percent | float | Percentage of energy supplied from renewable sources at the data center during the logging interval0 to 100 · optional | 94.5 |
carbon_emissions_kgco2e | float | Estimated carbon emissions (in kg CO2 equivalent) associated with the energy consumed during the logging interval0 or more · optional | 0.39 |
uptime_seconds | integer | Number of seconds the server has been continuously operational at the time of logging0 or more · optional | 7742321 |
| Dates and times 1 column | |||
timestamp | datetime | Date and time when the energy usage was recorded (UTC recommended) | 2024-05-01T08:14:23Z |
Use it for
A gaming dashboard
Cpu_
utilization_ percent by server_ status and a breakdown of server_ name. Excel, Power BI or Tableau. Why do the 51 active rows have a mean cpu_
utilization_ percent of 66.0? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Logs120LOG-000177.4activeLOG-000265.2activeLOG-000392.6active
A software demo
Believable logs with server_
id, server_ name and data_ center_ id to fill a screen in front of a buyer.
blueprint · gaming-server-energy-usage-logs
Behind this dataset
Same schema. As many rows as you need.
These 120 rows came out of a blueprint — 16 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
- Each row represents one hourly interval per server.
- Energy usage (kWh) must be recorded for every interval.
- Include server location and hardware type to allow segmentation.
- Flag intervals exceeding threshold for further investigation.
- Each server must have at least three consecutive intervals logged.
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- gaming-server-energy-usage-logs