Gaming
18 columns
75 rows
8 formats

Gaming Cloud Resource Optimization Logs

This dataset contains detailed logs of resource allocation, server usage, and optimization events in multiplayer cloud gaming environments. It includes granular metrics on CPU, memory, GPU, bandwidth, and storage usage, as well as sustainability indicators like energy consumption and carbon emissions. Ideal for research and development in dynamic cloud resource management, operational efficiency, and sustainable gaming infrastructure.

last updated 16 Jan 2026
by GoMask

The brief that made it

AI/ML model development for dynamic cloud resource allocation

Sample rows

preview · 8 of 75 rows · all 18 columns

log_idstring	event_typestring	server_utilization_percentfloat	optimization_resultstring	timestampdatetime	server_idstring	game_session_idstring	resource_cpu_coresinteger	resource_memory_gbfloat	resource_gpu_countinteger	resource_bandwidth_mbpsfloat	resource_storage_gbfloat	optimization_algorithmstring	player_countinteger	regionstring	energy_consumption_kwhfloat	carbon_emission_kgfloat	notesstring
LOG-0001	allocation	78.2	blank	2023-11-05T10:13:32Z	SRV-EU-17	GS-10432	16	64	2	900.5	1200	blank	45	europe-west	4.8	2.7	High player load, allocated extra resources.
LOG-0002	scaling	92.5	blank	2023-11-05T10:18:11Z	SRV-US-03	GS-10711	32	128	4	1500	2500	blank	80	us-east	8.5	4.2	Auto-scaling triggered due to increased demand.
LOG-0003	deallocation	38.4	blank	2023-11-05T10:23:54Z	SRV-AP-09	GS-10222	8	32	1	350	600	blank	22	asia-south	1.1	0.4	Session ended, resources deallocated.
LOG-0004	migration	65.1	blank	2023-11-05T10:29:43Z	SRV-EU-17	blank	24	96	3	1200	1700	blank	blank	europe-west	5.6	2.1	Migrated workloads to Europe West for latency optimization.
LOG-0005	failure	0	blank	2023-11-05T10:36:10Z	SRV-US-21	blank	0	0	0	0	0	blank	blank	us-central	0	0	Unexpected hardware failure detected.
LOG-0006	optimization	52.8	improved	2023-11-05T10:41:08Z	SRV-AP-09	blank	12	48	1	650	900	DynamicBinPack	blank	asia-south	2.3	0.9	Bin packing reduced resource waste.
LOG-0007	allocation	41.6	blank	2023-11-05T10:46:12Z	SRV-EU-05	GS-10476	8	32	1	400	700	blank	18	europe-north	1.3	0.6	Standard game allocation.
LOG-0008	optimization	85.6	success	2023-11-05T10:52:47Z	SRV-US-03	GS-10711	28	112	4	1280	2250	PowerSaveV2	77	us-east	7.3	3.7	Energy savings after optimization.
LOG-0009	scaling	64.2	blank	2023-11-05T10:59:21Z	SRV-EU-05	GS-10999	16	64	2	800	1300	blank	40	europe-north	2.7	1.2	Player spike caused scaling.
LOG-0010	failure	0	blank	2023-11-05T11:04:32Z	SRV-AP-20	blank	0	0	0	0	0	blank	blank	asia-east	0	0	Power outage in Asia East DC.
LOG-0011	allocation	53.5	blank	2023-11-05T11:10:19Z	SRV-US-03	GS-10888	12	48	2	570	800	blank	32	us-east	2.1	1	New tournament session allocation.
LOG-0012	optimization	57	improved	2023-11-05T11:15:51Z	SRV-EU-17	blank	20	80	2	950	1500	LoadBalancerX	blank	europe-west	4.1	1.8	Load balanced across nodes.
LOG-0013	deallocation	28.9	blank	2023-11-05T11:20:14Z	SRV-AP-11	GS-11001	6	24	1	220	350	blank	8	asia-south	0.7	0.3	Small session wrapped up.
LOG-0014	migration	59.3	blank	2023-11-05T11:25:50Z	SRV-EU-05	blank	12	48	1	650	925	blank	blank	europe-north	1.8	0.8	Migrated to optimize network costs.
LOG-0015	optimization	60	success	2023-11-05T11:30:32Z	SRV-US-21	blank	24	96	3	1400	1900	GreenOpt	blank	us-central	6.7	2.9	Green optimization resulted in lower emissions.
LOG-0016	allocation	73.1	blank	2023-11-05T11:35:11Z	SRV-AP-20	GS-11220	16	64	2	900	1100	blank	52	asia-east	3.9	1.7	Peak hour allocation.
LOG-0017	migration	77.5	blank	2023-11-05T11:40:27Z	SRV-US-03	blank	28	112	4	1350	2300	blank	blank	us-east	6.8	3.2	Migration to US East for special event.
LOG-0018	scaling	59.9	blank	2023-11-05T11:45:13Z	SRV-AP-09	GS-10565	10	40	1	420	850	blank	25	asia-south	1.8	0.7	Session upgraded due to player count.
LOG-0019	failure	0	blank	2023-11-05T11:51:00Z	SRV-EU-17	blank	0	0	0	0	0	blank	blank	europe-west	0	0	Network interface failure.
LOG-0020	deallocation	34.1	blank	2023-11-05T11:56:37Z	SRV-US-21	GS-11002	12	48	2	600	900	blank	19	us-central	1.2	0.5	Resources released after session.

What the 75 rows show

from the 75-row sample

Failure (event type) stands out: mean server_utilization_percent is 0.0, against 58.9 for the rest.

59.3median server_utilization_percent
13regions
12median resource_cpu_cores
48.0median resource_memory_gb
2median resource_gpu_count
665.1median resource_bandwidth_mbps

Mean server_utilization_percent by event_type75 rows

server_utilization_percent75 rows, in bands of 10

Median 59.3, from 0.0 to 95.3.

optimization_result15 rows with a value · 60 left blank

improved8
success5
unchanged1
failure1

18 columns by typefrom the column list below

string 8
integer 3
float 6
datetime 1

Columns

18 columns in three groups

blueprint · 18 columns
column	type	description	example
Text 8 columns
`log_id`	string	Unique identifier for each log entryunique	LOG-0001
`server_id`	string	Unique identifier for the cloud server involved in the event	SRV-EU-17
`game_session_id`	string	Unique identifier for the multiplayer game sessionoptional	GS-10432
`event_type`	string	Type of event (e.g., allocation, deallocation, optimization, scaling, failure, migration)6 values	allocation
`optimization_algorithm`	string	Name of the optimization algorithm or strategy applied (if any)optional	DynamicBinPack
`optimization_result`	string	Outcome or result of the optimization event (e.g., success, failure, improved, unchanged)success · failure · improved · unchanged · optional	improved
`region`	string	Geographic region or data center location of the serveroptional	europe-west
`notes`	string	Additional notes or comments related to the eventoptional	Peak hour allocation.
Numbers 9 columns
`resource_cpu_cores`	integer	Number of CPU cores allocated or used during the event0 or more · optional	16
`resource_memory_gb`	float	Amount of memory (in GB) allocated or used during the event0 or more · optional	64
`resource_gpu_count`	integer	Number of GPUs allocated or used during the event0 or more · optional	2
`resource_bandwidth_mbps`	float	Network bandwidth (in Mbps) allocated or used during the event0 or more · optional	900.5
`resource_storage_gb`	float	Amount of storage (in GB) allocated or used during the event0 or more · optional	1200
`server_utilization_percent`	float	Overall server utilization as a percentage (0-100)0 to 100 · optional	78.2
`player_count`	integer	Number of active players in the game session during the event0 or more · optional	45
`energy_consumption_kwh`	float	Estimated energy consumption (in kWh) during the event0 or more · optional	4.8
`carbon_emission_kg`	float	Estimated carbon emissions (in kg CO2e) during the event0 or more · optional	2.7
Dates and times 1 column
`timestamp`	datetime	Date and time when the log entry was recorded	2023-11-05T10:13:32Z

Use it for

A gaming dashboard
Server_utilization_percent by event_type and a breakdown of optimization_result. Excel, Power BI or Tableau.
Why do the 10 failure rows have a mean server_utilization_percent of 0.0?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
Logs75
LOG-000178.2allocati…
LOG-000292.5scaling
LOG-000338.4dealloca…
A software demo
Believable logs with timestamp, server_id and game_session_id to fill a screen in front of a buyer.

This dataset75 rows18 columns

Yours1,000 rows18 columnsregion: UK only

blueprint · gaming-cloud-resource-optimization-logs

Behind this dataset

Same schema. As many rows as you need.

These 75 rows came out of a blueprint — 18 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.

Rules it was built with

Each row represents a unique resource allocation event with timestamp.
Include server region, game instance type, allocated CPU/GPU resources, and duration.
Track optimization actions (e.g., scaling, load balancing) and their triggers.
Anonymize all sensitive identifiers; no player-level data.
Include an efficiency score calculated post-event.

Rows1,000 rows10,000 rows100,000 rows1,000,000 rows

Open the blueprint in Data Factory

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-cloud-resource-optimization-logs

What should your data show?

No signup. No card.

Sample rows

What the 75 rows show

Columns

Use it for

A gaming dashboard

A root-cause class exercise

A software demo

Make it yours.

Same schema. As many rows as you need.

More in Gaming

What should your data show?