Problems / RAG and retrieval, hard

GraphRAG index shared with ingestion

The GraphRAG index answers questions and absorbs entity extraction from new documents at the same time, at 1,500 operations a second.

Free to open. Runs in your browser, no sign-up.

Your goals

Success ≥ 99%, p99 ≤ 5 s.

The traffic

1,500 requests a second for 30 seconds: 100% request (reads).

The system

What each component does in this design, and what calls it. The simulator mimics each one from these settings.

ComponentIts job hereSettings
Load balancerLoad balancerTraffic 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 serviceLoad balancer forwards to it.Calls GraphRAG index.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.3 replicas × 500 slots · timeout 30 s
GraphRAG indexGraphRAG indexAI app calls it.GraphRAG builds a knowledge graph from documents so multi-hop questions can follow relationships.64 slots

Hints

Try it first. Open one hint at a time if you get stuck.

Hint 1

Ingestion and queries share CPU.

Hint 2

Follow one question through each retrieval stage; the stage that turns red is the one to fix first.

One way to solve it

Add GraphRAG capacity (or separate the build from serving).

More rag and retrieval problems