Quiz collegato alla guida · Medio Livello
Quiz sugli endpoint del modello di test di carico
Pianifica test di carico degli endpoint realistici utilizzando modelli di arrivo, input rappresentativi, percentili di latenza, misure delle risorse e controlli di test sicuri.
Domanda 1 di 8
Quale set di metriche offre una visione più ampia della capacità di un endpoint di modello rispetto alla sola latenza media?
Anteprima di ogni domanda8 domande
Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.
- Quale set di metriche offre una visione più ampia della capacità di un endpoint di modello rispetto alla sola latenza media?
- Training accuracy and validation loss
- Mean request size and model parameter count
- Throughput, latency percentiles, errors, and resource use
- Source-file count and deployment age
- In che modo un test a circuito chiuso con utenti virtuali può nascondere un sovraccarico?
- It creates an unlimited arrival rate regardless of response time
- Waiting users reduce their request rate as responses slow
- It records only successful requests
- It applies a fixed arrival rate independent of user behavior
- Perché includere diverse dimensioni di payload in un test di endpoint di modello?
- Payload length determines the endpoint license
- All tensor shapes require identical compute and memory
- Large payloads cannot be tested safely
- Input dimensions or sequence lengths can change compute and memory
- Cosa distingue uno soak test da un breve load test?
- It measures only startup latency before any request
- It repeats one request until its response is cached
- It runs long enough to reveal gradual degradation such as leaks
- It varies model architecture while keeping duration brief
- Perché testare separatamente i percorsi di serving a freddo e a caldo?
- Cold requests always have lower latency than warm ones
- Warm requests bypass the model and use a different API
- Startup and model loading can add latency beyond steady inference
- Cold and warm requests differ only in labels
- What can make a load generator provide misleading results?
- Recording latency makes the generator invalid
- The generator can saturate on CPU, network, or serialization before reaching target load
- Python scenarios cannot generate concurrent requests
- A load generator cannot affect measured throughput
- Why define stop conditions and monitor dependent services during a stress test?
- Stop conditions guarantee that the endpoint cannot fail
- Monitoring dependencies removes them from the test
- Stress traffic should be bounded to avoid affecting other systems
- A stress test should disable all infrastructure metrics
- What does Locust provide for a load test?
- Python-defined scenarios with throughput, response-time, and error reporting
- An automatic proof that production capacity will be sufficient
- A pretrained model that serves predictions
- A guarantee that the generator has unlimited capacity