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 "Queue Checkpoint Restore": Queue Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for asynchronous work buffer. 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 Queue Checkpoint Restore when the queue depth increased, so the team could recover long-running work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Cache Image Hardening": Cache Image Hardening is a compute security practice that reduces risk inside packaged runtime images for fast temporary data layer. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The platform engineering team used Cache Image Hardening when the cache missed during peak traffic, so the team could ship safer workloads before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "GPU Checkpoint Restore": GPU Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for accelerated compute for parallel workloads. 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 GPU Checkpoint Restore when the training job requested more memory, so the team could recover long-running work before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Storage Placement Strategy": Storage Placement Strategy is a compute scheduling rule that chooses where workloads should run for persistent data and object access. 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 Storage Placement Strategy when the workload read a large dataset, so the team could improve reliability and efficiency before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "Scheduler Workload Priority": Scheduler Workload Priority is a compute scheduling signal that tells the platform which work matters most when capacity is constrained for placement of work onto resources. 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 Scheduler Workload Priority when the cluster needed to place a job, so the team could protect critical paths before the workload scaled up.”
機械支援の翻訳下書き (Japanese) for "GPU Cold Start Budget": GPU Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for accelerated compute for parallel workloads. 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 GPU Cold Start Budget when the training job requested more memory, so the team could keep first requests responsive before the workload scaled up.”
機械支援の翻訳下書き (Japanese) 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.”
機械支援の翻訳下書き (Japanese) for "TLS Ingress Rule": TLS Ingress Rule is a networking boundary rule that controls how external traffic enters a service for encrypted transport setup. 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 TLS Ingress Rule when a certificate neared expiration, so the team could keep entry points predictable before traffic crossed a service boundary.”
機械支援の翻訳下書き (Japanese) for "Observability Rollback Plan": Observability Rollback Plan is a devops recovery plan that defines how to return to a known good version for logs, metrics, traces, and events. It uses version pins, database notes, and operator steps so teams can recover quickly from bad changes while keeping evidence, reliability, and public-safe operational boundaries clear.
“例文の下書き: The DevOps team used Observability Rollback Plan when latency increased after deploy, so the team could recover quickly from bad changes before the deployment window opened.”
機械支援の翻訳下書き (Japanese) for "Scheduler Cold Start Budget": Scheduler Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for placement of work onto resources. 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 Scheduler Cold Start Budget when the cluster needed to place a job, so the team could keep first requests responsive before the workload scaled up.”