Problems / RAG and retrieval, easy
Every question is embedded first, but the embedding deployment allows 8 concurrent calls at 400 questions a second.
Free to open. Runs in your browser, no sign-up.
Success ≥ 99%, time to first token p99 ≤ 2.5 s.
400 requests a second for 30 seconds: 100% request (reads).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls AI app.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| AI appApp service | Load balancer forwards to it.Calls Embedding model, GPU serving pool.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 500 slots · timeout 30 s |
| Embedding modelEmbedding model | AI app calls it.Embeddings turn text into vectors where similar meanings sit close together. | – |
| GPU serving poolSelf-hosted serving pool | AI app calls it.GPU servers batch requests together; throughput rises with batch size until memory runs out. | 2000 slots |
Try it first. Open one hint at a time if you get stuck.
8 calls ÷ 25 ms ≈ 320 a second.
Follow one question through each retrieval stage; the stage that turns red is the one to fix first.
Raise the embedding model’s concurrency.