OCI High Performance Workloads · Stockholm

When players arrive,
the platform responds.

A live view of the Game-HPW event path. Only observed values are shown as live. Capacity and performance figures appear when their measurement pipeline is ready.

Connecting to HPW…

Incoming traffic

—active game sessions15-second cache freshness window

—active simulated sessionsGenerator activity; observed, not requested target

—completed generator requests / second10-second measurement window

Two real service paths

HPW cloud illustrationTemporary visual placeholder. The supplied cloud artwork will replace this without changing live data labels.

Event ingestionAPI Gateway → Functions → Streaming → OKE worker → Autonomous Database + Object Storage

Interactive pathAPI Gateway → internal Load Balancer → OKE API ↔ OCI Cache

Platform signals

OKE APIUnknown

StreamingUnknown

OCI CacheUnknown

Autonomous DatabaseUnknown

Object StorageUnknown

p95 / p99 latencyNot measured

Ready OKE nodesNot instrumented

Measured run accounting

Waiting for the measurement service

GenerationUnavailable

Durable completionNo reconciliation observed

API processesUnavailable

WorkerUnavailable

API route latency · last 60 seconds

Waiting for samples

Pod CPU and memory

Waiting for Kubernetes measurements

Durable completion compares acknowledged unique IDs against both ADB and Object Storage. Worker deliveries can include retries. Small samples do not establish a reliable p99. CPU below is Node process consumption; pod measurements are shown only when Kubernetes supplies them.