What problem does it solve? Measuring the real performance of a model served on MAX requires driving load against a live endpoint and interpreting throughput and latency numbers correctly. This Skill guides you through running max benchmark against a max serve endpoint so you get trustworthy tokens/sec, TTFT, and TPOT figures instead of garbage or misleading results. ## Core Features & Use Cases - Workload Selection: Match the benchmark workload to your question, from single-request latency at concurrency 1 to concurrency and request-rate sweeps that reveal peak throughput and the latency knee. - Result Capture and GPU Stats: Save runs to JSON with --result-filename, stamp them with --metadata, and collect GPU utilization and peak memory with --collect-gpu-stats. - Troubleshooting Guidance: Diagnose connection failures, model-name mismatches, tokenizer-alias errors, chat-template 400s, and flat throughput caused by a server batch-size cap. - Use Case: You just deployed a model with max serve and need to know whether it can hold a TTFT p99 under 500 ms at production load. Run a concurrency sweep, read the highest concurrency that meets the SLA, and save the stamped JSON for comparison with future builds. ## Quick Start Ask the AI to benchmark the model currently served on localhost:8000 with a concurrency sweep and save the results to a JSON file.