Quiz collegato alla guida · Medio Livello

Quiz sulla risoluzione dei colli di bottiglia del caricatore dati

Diagnostica i ritardi della pipeline di input e ottimizza il conteggio dei lavoratori, il precaricamento, la memoria bloccata, il layout di archiviazione e i trasferimenti utilizzando prove misurate.

Domanda 1 di 8

Quale sintomo suggerisce che la pipeline di input sta limitando l'addestramento?

Anteprima di ogni domanda8 domande

Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.

  1. Quale sintomo suggerisce che la pipeline di input sta limitando l'addestramento?
    • GPU compute stays continuously active while the next batch is prepared
    • The loader places each batch in the device queue before current computation ends
    • The GPU waits between steps while batches are prepared
    • A full prefetch queue is available while the GPU remains idle
  2. Perché aumentare i worker del DataLoader può alla fine ridurre le prestazioni?
    • More workers always increase throughput without resource cost
    • Workers can contend for CPU, memory, or storage resources
    • Worker count changes model weights
    • Workers guarantee every data source becomes sequential
  3. Con cosa aiuta la memoria host bloccata (pinned memory) in un flusso di lavoro compatibile?
    • Reduce file-read latency from remote object storage
    • Lower CPU image or audio decoding time
    • Increase the GPU’s physical VRAM capacity
    • Improve host-to-GPU data transfer in a compatible workflow
  4. In che modo il prefetching influisce sulla preparazione dei batch?
    • Prepare future batches before the model needs them
    • Keep the entire dataset resident in GPU memory
    • Skip preprocessing for all later epochs
    • Start reading each next batch only after the current device step ends
  5. Perché un dataset composto da molti file minuscoli potrebbe caricarsi lentamente?
    • When every read is a large sequential transfer that saturates bandwidth
    • When model kernels, rather than storage access, saturate GPU compute
    • When metadata lookups and file opens dominate reads
    • When optimizer state occupies accelerator memory
  6. What should be verified after adding a cache or faster transform?
    • Whether the worker count matches the previous run
    • Confirm data values and labels still match the intended pipeline
    • Check that cache capacity uses all available RAM
    • Whether GPU utilization rises after any transformation
  7. When can non-blocking device copies improve a pipeline?
    • Whenever any tensor is copied, whether or not execution overlaps
    • Only when model weights are frozen
    • When the host has no memory pressure
    • When transfer can overlap with compute under the runtime and stream setup
  8. What should be done before changing several loader settings at once?
    • Profile a baseline and vary settings in controlled comparisons
    • Increase worker and prefetch settings together without measuring
    • Optimize kernels before measuring input wait time
    • Enable pinned memory for every device unconditionally