Skip to content

Practical Experience, Troubleshooting, and Selection

This series no longer explains "what it is" by component, but starts from a specific problem and provides evidence chains, experimental variables, acceptance criteria, and stopping conditions. The numbers on the page should be measured on target hardware and real workloads; example values cannot replace production baselines.

Troubleshooting and Incidents

Performance, Cost, and Capacity

Platform and Scheduling

End-to-End Delivery

Reading and Reproduction Conventions

Each experiment records at least the following:

  1. Kubernetes, driver, CUDA/ROCm/CANN, and component versions;
  2. GPU/NPU/TPU, CPU, memory, disk, and network topology;
  3. Model, precision, input/output length, and concurrency distribution;
  4. Cold cache/hot cache, failure retries, and warm-up status;
  5. Raw logs, events, metrics, traces, and timestamps;
  6. Success criteria, failure criteria, and the scope of inapplicability of results.

When reproducing experiments, first modify Namespace, images, StorageClass, resource names, and security policies. Do not directly copy permissions, image tags, or cloud provider parameters from the examples into production.