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 "Cluster Placement Strategy": 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.”
機械支援の翻訳下書き (Japanese) for "Queue Workload Priority": Queue Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for asynchronous work buffer. 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 Queue Workload Priority when the queue depth increased, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Runbook Release Manifest": Runbook Release Manifest is a devops delivery record that lists versions, artifacts, routes, and checks for a release for documented operational procedure. It uses commit IDs, checksums, and deployment URLs so teams can make releases auditable while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Runbook Release Manifest when a responder needed the recovery steps, so the team could make releases auditable before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Queue Placement Strategy": Queue Placement Strategy is a compute scheduling rule that chooses where workloads should run for asynchronous work buffer. 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 Queue Placement Strategy when the queue depth increased, so the team could improve reliability and efficiency before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "CPU Checkpoint Restore": CPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for general-purpose processor scheduling. 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 CPU Checkpoint Restore when the service hit a compute ceiling, so the team could recover long-running work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "DNS Traffic Shaper": DNS Traffic Shaper is a networking control mechanism that limits or prioritizes flows across links for name resolution and delegation. It uses queues, rate limits, and quality-of-service rules so teams can protect important traffic while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The network engineering team used DNS Traffic Shaper when a resolver returned stale data, so the team could protect important traffic before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "BGP Rate Limit": BGP Rate Limit is a networking traffic control that caps request volume over a period for interdomain routing. 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 BGP Rate Limit when a route advertisement changed, so the team could protect services from overload before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "CPU Runtime Profile": 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.”
機械支援の翻訳下書き (Japanese) for "CPU Workload Priority": CPU Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for general-purpose processor scheduling. 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 CPU Workload Priority when the service hit a compute ceiling, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scheduler Autoscaling Policy": Scheduler Autoscaling Policy is a compute control loop that changes capacity based on demand signals for placement of work onto resources. 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 Scheduler Autoscaling Policy when the cluster needed to place a job, so the team could match resources to load before the workload scaled up.”