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
機械支援の翻訳下書き (Japanese) for "GPU Workload Priority": 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.”
機械支援の翻訳下書き (Japanese) for "Scheduler Isolation Boundary": 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.”
機械支援の翻訳下書き (Japanese) for "GPU Capacity Forecast": GPU Capacity Forecast is a compute planning model that estimates future resource needs for accelerated compute for parallel workloads. 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 GPU Capacity Forecast when the training job requested more memory, so the team could avoid surprise shortages before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Edge Cache Invalidation": Edge Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for globally distributed runtime. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Edge Cache Invalidation when the request arrived near a user, so the team could serve current results before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Incident Approval Step": Incident Approval Step is a devops workflow control that requires review before a sensitive change proceeds for response to service degradation. It uses role checks, comments, and audit logs so teams can keep high-risk automation accountable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Incident Approval Step when on-call received a high-severity page, so the team could keep high-risk automation accountable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Virtual Machine Cold Start Budget": Virtual Machine Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for isolated guest compute. 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 Virtual Machine Cold Start Budget when the VM migrated hosts, so the team could keep first requests responsive before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Memory Resource Quota": Memory Resource Quota is a compute limit that sets how much compute a workload may consume for volatile runtime storage. 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 Memory Resource Quota when the process approached its memory limit, so the team could protect shared capacity before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Infrastructure Incident Timeline": 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.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) 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.”