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
机器辅助翻译草稿 (Chinese) for "Scheduler Runtime Profile": Scheduler Runtime Profile is a compute performance record that shows how code uses CPU, memory, I/O, and time for placement of work onto resources. 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 Scheduler Runtime Profile when the cluster needed to place a job, so the team could target optimization work before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "BGP Ingress Rule": BGP Ingress Rule is a networking boundary rule that controls how external traffic enters a service for interdomain routing. It uses hostnames, paths, protocols, and policy checks so teams can keep entry points predictable while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used BGP Ingress Rule when a route advertisement changed, so the team could keep entry points predictable before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "DNS Rate Limit": DNS Rate Limit is a networking traffic control that caps request volume over a period for name resolution and delegation. It uses identity keys, windows, and response policies so teams can protect services from overload while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The network engineering team used DNS Rate Limit when a resolver returned stale data, so the team could protect services from overload before traffic crossed a service boundary.”
机器辅助翻译草稿 (Chinese) for "Incident Rollout Guard": Incident Rollout Guard is a devops release control that limits exposure during gradual deployment for response to service degradation. It uses traffic slices, health checks, and automatic pause rules so teams can reduce blast radius while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Incident Rollout Guard when on-call received a high-severity page, so the team could reduce blast radius before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Serverless Cold Start Budget": Serverless Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for event-driven function execution. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Serverless Cold Start Budget when the function received a traffic burst, so the team could keep first requests responsive before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "CPU Isolation Boundary": CPU Isolation Boundary is a compute security boundary that separates workloads so one cannot affect another unexpectedly for general-purpose processor scheduling. 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 CPU Isolation Boundary when the service hit a compute ceiling, so the team could reduce cross-workload risk before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Incident Runbook Check": Incident Runbook Check is a devops operational test that confirms that documented procedures still work for response to service degradation. It uses dry runs, screenshots, and command validation so teams can keep response playbooks current while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The DevOps team used Incident Runbook Check when on-call received a high-severity page, so the team could keep response playbooks current before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Scheduler Checkpoint Restore": Scheduler Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for placement of work onto resources. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Scheduler Checkpoint Restore when the cluster needed to place a job, so the team could recover long-running work before the workload scaled up.”
机器辅助翻译草稿 (Chinese) for "Release Incident Timeline": Release Incident Timeline is a devops response record that orders alerts, actions, and decisions during an incident for versioned delivery of code or content. 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 Release Incident Timeline when the release notes were generated, so the team could learn from outages without guesswork before the deployment window opened.”
机器辅助翻译草稿 (Chinese) for "Memory Capacity Forecast": Memory Capacity Forecast is a compute planning model that estimates future resource needs for volatile runtime storage. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
“示例草稿: The platform engineering team used Memory Capacity Forecast when the process approached its memory limit, so the team could avoid surprise shortages before the workload scaled up.”