← 📈 Observability & Reliability
Core
JMeter performance testing: workload models, assertions and credible results
Build a bounded JMeter test and distinguish closed-user load from independent arrivals. Validate response assertions, achieved throughput and generator health before using latency percentiles to approve a release.
a free account opens the core tier · no card
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Cloud Platforms & ArchitectureYour service autoscales on CPU and still falls over during traffic spikes. Why, and what would you scale on instead?→Incident Response & Production DebuggingYour p99 latency is three seconds while the average is two hundred milliseconds. Where do you look?→Incident Response & Production Debuggingp99 spikes, probes time out, CPU utilisation reads 30 percent and nothing is OOMKilled. cpu.stat shows nr_throttled climbing. Explain it.→AI & GPU InfrastructureYou have eight 80GB GPUs and a 70B model. Tensor parallel across all eight, or two replicas of four? Defend the choice.→AI & GPU InfrastructureProduct wants to raise the context limit from 8k to 128k tokens. What happens to your infrastructure?→AI & GPU InfrastructureLong prompts are making short requests slow on the same replica. What is happening, and how would you fix it?→