Bài kiểm tra có liên kết hướng dẫn · Trung bình Cấp độ

Giám sát việc sử dụng GPU với nvidia-smi và DCGM Quiz

Giải thích thời gian bận rộn của GPU, hoạt động của bộ nhớ so với công suất, sức mạnh và các chỉ số về tình trạng, đồng thời sử dụng tính năng lập hồ sơ để tìm ra các tắc nghẽn thực tế.

Đường dẫn hướng dẫn liên quanGiám sát việc sử dụng GPU Nvidia Smi Dcgm
Câu hỏi 1 của 8

What does nvidia-smi GPU utilization approximately report?

Xem trước mọi câu hỏi8 câu hỏi

Câu trả lời và giải thích xuất hiện khi bạn làm bài kiểm tra.

  1. What does nvidia-smi GPU utilization approximately report?
    • The fraction of peak FLOPs achieved by the GPU
    • The percentage of total VRAM allocated to a process
    • The share of a sample period with one or more kernels executing
    • The amount of device memory currently allocated
  2. How does memory utilization differ from memory usage?
    • GPU busy time versus VRAM capacity in gigabytes
    • Memory activity over time versus allocated memory capacity
    • Two names for tensor-core activity
    • The same counter reported in different units
  3. A GPU reports high utilization but low throughput. What is a plausible explanation?
    • The utilization field directly measures peak FLOPs
    • A busy GPU must be compute-bound
    • High allocated memory proves device-memory bandwidth is saturated
    • The workload may be memory-bound or use inefficient kernels
  4. What might low GPU activity between training steps indicate?
    • The input pipeline or synchronization may be stalling the device
    • Low utilization proves all model parameters fit in VRAM
    • A longer step means the training run is overfit
    • The model must be using tensor cores at peak throughput
  5. Which DCGM metric can help assess memory-traffic activity?
    • SM occupancy ratio
    • GPU memory allocated in MiB
    • DRAM activity or utilization ratio
    • Tensor-pipe activity ratio
  6. What can temperature, clocks, and power help diagnose?
    • Whether the model has class imbalance
    • Thermal or power constraints affecting performance
    • Whether data-loader workers have duplicate samples
    • Whether a model uses grouped-query attention
  7. When should an engineer use a framework profiler after reading DCGM metrics?
    • When a DCGM field shows the exact source line of a slow kernel
    • When a kernel fails to compile before any execution telemetry exists
    • Before collecting aggregate metrics so the profiler has a baseline
    • When aggregate telemetry cannot identify the slow kernel or operator
  8. Why record sampling period and hardware context with utilization data?
    • Sampling interval and device details affect metric interpretation
    • The sampling period has no effect because the counter is instantaneous
    • Device details determine model output labels
    • Recording context guarantees equal throughput across runs