Quiz collegato alla guida · Medio Livello
Quiz sull'inferenza della GPU serverless e sugli avviamenti a freddo
Identifica le fasi di avvio a freddo nell'inferenza della GPU serverless e scegli le mitigazioni bilanciando la latenza, la capacità di riscaldamento, la memorizzazione nella cache e i costi.
Domanda 1 di 8
Quale richiesta sta sperimentando più direttamente un cold start su un endpoint GPU serverless?
Anteprima di ogni domanda8 domande
Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.
- Quale richiesta sta sperimentando più direttamente un cold start su un endpoint GPU serverless?
- A request routed to a worker that is already initialized
- A request waiting behind other work on a warm but saturated worker
- The first request that must wait for a new worker and runtime to initialize
- A request delayed only by model computation after startup
- Quale passaggio trasferisce specificamente i parametri del modello nella memoria GPU durante l'avvio?
- Pulling the container image
- Loading model weights into accelerator memory
- Allocating the GPU worker
- Starting the runtime process
- Perché un benchmark warm-path può sottovalutare la latenza di un endpoint che scala a zero?
- A warm benchmark includes container and model startup on every call
- Warm measurements omit startup and initialization paid by the first request after scale-up
- A warm benchmark includes worker allocation after the container is ready
- A warm benchmark reloads the model weights on every request
- Quale mitigazione può ridurre i cold start aumentando le spese in idle?
- Keeping a minimum amount of GPU capacity ready
- Deleting model artifacts after every request
- Increasing the model image size to force preloading
- Retrying every request without a limit
- Perché separare i tempi di fase cold-start?
- Identify whether queueing, worker setup, model loading or initialization dominates delay
- Determine whether generated text has correct semantics
- Measure steady-state GPU throughput only
- Select the model confidence threshold
- How can aggressive retries worsen a cold-start incident?
- They add more in-flight work while workers may still be starting
- They guarantee the platform keeps a GPU warm without billing
- They automatically deduplicate all repeated requests
- They skip model initialization on retry
- Which measurements distinguish cold and warm behavior?
- Only training accuracy
- Latency distributions for each path and cold-start frequency
- Only average GPU memory
- Only container build time
- What does serverless imply about inference cost?
- It can reduce infrastructure management, but usage and warm capacity may still cost money
- It is automatically free when idle in every provider
- GPU capacity has no billing limits
- Retries remove compute charges