Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
2,337 definitions
CPU Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for general-purpose processor scheduling. It uses sampling, traces, and resource metrics so teams can target optimization work while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used CPU Runtime Profile when the service hit a compute ceiling, so the team could target optimization work before the workload scaled up.”
Infrastructure Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for cloud resources and platform wiring. It uses timestamps, owners, and evidence links so teams can learn from outages without guesswork while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Infrastructure Incident Timeline when a new region was added, so the team could learn from outages without guesswork before the deployment window opened.”
Scheduler Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for placement of work onto resources. It uses namespaces, sandboxes, and access controls so teams can reduce cross-workload risk while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Scheduler Isolation Boundary when the cluster needed to place a job, so the team could reduce cross-workload risk before the workload scaled up.”
Virtual Machine Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for isolated guest compute. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Virtual Machine Workload Priority when the VM migrated hosts, so the team could protect critical paths before the workload scaled up.”
GPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for accelerated compute for parallel workloads. It uses priority classes, preemption rules, and fairness limits so teams can protect critical paths while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used GPU Workload Priority when the training job requested more memory, so the team could protect critical paths before the workload scaled up.”
Cluster Placement Strategy is a compute scheduling rule that chooses where workloads should run for group of machines acting as one platform. It uses affinity, topology, availability, and cost signals so teams can improve reliability and efficiency while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cluster Placement Strategy when the cluster added a node pool, so the team could improve reliability and efficiency before the workload scaled up.”
Serverless Autoscaling Policy is a compute control loop that changes capacity based on demand signals for event-driven function execution. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Serverless Autoscaling Policy when the function received a traffic burst, so the team could match resources to load before the workload scaled up.”
Runbook Infra Plan is a devops change preview that shows expected infrastructure changes before apply for documented operational procedure. It uses resource graphs, policy checks, and cost notes so teams can review platform changes safely while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Runbook Infra Plan when a responder needed the recovery steps, so the team could review platform changes safely before the deployment window opened.”
Secret Artifact Signature is a devops supply-chain record that proves that an artifact came from an expected build path for credential and sensitive configuration. It uses cryptographic signatures, provenance, and verification so teams can trust deployed packages while keeping evidence, reliability, and public-safe operational boundaries clear.
“The DevOps team used Secret Artifact Signature when a token rotated, so the team could trust deployed packages before the deployment window opened.”
Cluster Resource Quota is a compute limit that sets how much compute a workload may consume for group of machines acting as one platform. It uses policy, reservations, and usage tracking so teams can protect shared capacity while keeping evidence, reliability, and public-safe operational boundaries clear.
“The platform engineering team used Cluster Resource Quota when the cluster added a node pool, so the team could protect shared capacity before the workload scaled up.”