GraphQL Federation Benchmark
An open benchmark of GraphQL federation routers/gateways. Each router is evaluated under the same conditions, on the same machine with the same subgraphs and the same GraphQL operation, so you can compare throughput, latency, memory and CPU on equal terms.
New results are published every day from a public workflow that anyone can inspect or rerun on their own hardware.
Latest run
- Run
- #402
- Completed
Results at a glance
Fusion is the fastest router in every scenario of run 402.
- Real-world
- 1,947 requests/s
- 4% faster than Hive Router
- Synthetic
- 2,653 requests/s
- 5.2% faster than Hive Router
- Burst traffic
- 2,733 requests/s
- 18.8% faster than Hive Router
Synthetic results
GraphQL Federation specification
RouterMedian requests/sHTTP requests per second, as the median across the measured runs.
2,653, highest reported
All metrics for Fusion Nightly
- p95 latency95% of requests completed within this time.
- 34.9 ms
- p99.9 latency99.9% of requests completed within this time.
- 101 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 401 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 98.00%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.0%
2,652
All metrics for Fusion Nightly
- p95 latency95% of requests completed within this time.
- 30.3 ms
- p99.9 latency99.9% of requests completed within this time.
- 52.8 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 403 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 95.80%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.7%
2,398
All metrics for Fusion
- p95 latency95% of requests completed within this time.
- 41.5 ms
- p99.9 latency99.9% of requests completed within this time.
- 140 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 386 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 98.00%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.2%
1,131
All metrics for feddi
- p95 latency95% of requests completed within this time.
- 69.9 ms
- p99.9 latency99.9% of requests completed within this time.
- 106 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 1,215 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 95.40%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±1.7%
| Router/gateway | Median requests/sHTTP requests per second, as the median across the measured runs. | p95 latency95% of requests completed within this time. | p99.9 latency99.9% of requests completed within this time. | Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes. | Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads. | ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure. | Run varianceHow much throughput varied across the measured runs, as the coefficient of variation. |
|---|---|---|---|---|---|---|---|
2,653, highest reported | 34.9 ms | 101 ms | 401 MiB | 98.00 % | 100% | ±2.0% | |
2,652 | 30.3 ms | 52.8 ms | 403 MiB | 95.80 % | 100% | ±2.7% | |
2,398 | 41.5 ms | 140 ms | 386 MiB | 98.00 % | 100% | ±2.2% | |
1,131 | 69.9 ms | 106 ms | 1,215 MiB | 95.40 % | 100% | ±1.7% |
Apollo Federation v2
RouterMedian requests/sHTTP requests per second, as the median across the measured runs.
2,571, highest reported
All metrics for Fusion Nightly
- p95 latency95% of requests completed within this time.
- 35.4 ms
- p99.9 latency99.9% of requests completed within this time.
- 77.2 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 402 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 98.50%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.1%
2,523
All metrics for Hive Router
- p95 latency95% of requests completed within this time.
- 30.1 ms
- p99.9 latency99.9% of requests completed within this time.
- 50.6 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 130 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 94.80%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±3.2%
1,679
All metrics for Grafbase Gateway
- p95 latency95% of requests completed within this time.
- 42.4 ms
- p99.9 latency99.9% of requests completed within this time.
- 64.0 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 120 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 88.70%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±1.3%
1,422
All metrics for Cosmo Router
- p95 latency95% of requests completed within this time.
- 54.9 ms
- p99.9 latency99.9% of requests completed within this time.
- 79.2 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 163 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 99.30%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±1.3%
1,289
All metrics for Caliban
- p95 latency95% of requests completed within this time.
- 60.6 ms
- p99.9 latency99.9% of requests completed within this time.
- 90.7 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 6,251 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 99.90%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.0%
521
All metrics for Hive Gateway · Router Runtime
- p95 latency95% of requests completed within this time.
- 125 ms
- p99.9 latency99.9% of requests completed within this time.
- 219 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 2,749 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 99.80%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±1.5%
446
All metrics for Apollo Router
- p95 latency95% of requests completed within this time.
- 158 ms
- p99.9 latency99.9% of requests completed within this time.
- 201 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 177 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 100.00%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±1.7%
377
All metrics for Apollo Router
- p95 latency95% of requests completed within this time.
- 185 ms
- p99.9 latency99.9% of requests completed within this time.
- 242 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 201 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 100.00%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±2.2%
264
All metrics for Apollo Gateway
- p95 latency95% of requests completed within this time.
- 203 ms
- p99.9 latency99.9% of requests completed within this time.
- 278 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 2,176 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 99.60%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±0.9%
261
All metrics for Hive Gateway
- p95 latency95% of requests completed within this time.
- 263 ms
- p99.9 latency99.9% of requests completed within this time.
- 597 ms
- Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes.
- 3,455 MiB
- Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads.
- 99.30%
- ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure.
- 100%
- Run varianceHow much throughput varied across the measured runs, as the coefficient of variation.
- ±0.9%
| Router/gateway | Median requests/sHTTP requests per second, as the median across the measured runs. | p95 latency95% of requests completed within this time. | p99.9 latency99.9% of requests completed within this time. | Peak memoryThe highest sampled resident memory (RSS) of the router process and its child processes. | Average CPUAverage utilization of the router’s 4 hardware threads. 100% means both of its cores are fully busy on both threads. | ReliabilityThe share of requests that passed the checks for HTTP status, GraphQL errors and response structure. | Run varianceHow much throughput varied across the measured runs, as the coefficient of variation. |
|---|---|---|---|---|---|---|---|
2,571, highest reported | 35.4 ms | 77.2 ms | 402 MiB | 98.50 % | 100% | ±2.1% | |
2,523 | 30.1 ms | 50.6 ms | 130 MiB | 94.80 % | 100% | ±3.2% | |
1,679 | 42.4 ms | 64.0 ms | 120 MiB | 88.70 % | 100% | ±1.3% | |
1,422 | 54.9 ms | 79.2 ms | 163 MiB | 99.30 % | 100% | ±1.3% | |
1,289 | 60.6 ms | 90.7 ms | 6,251 MiB | 99.90 % | 100% | ±2.0% | |
521 | 125 ms | 219 ms | 2,749 MiB | 99.80 % | 100% | ±1.5% | |
446 | 158 ms | 201 ms | 177 MiB | 100.00 % | 100% | ±1.7% | |
377 | 185 ms | 242 ms | 201 MiB | 100.00 % | 100% | ±2.2% | |
264 | 203 ms | 278 ms | 2,176 MiB | 99.60 % | 100% | ±0.9% | |
261 | 263 ms | 597 ms | 3,455 MiB | 99.30 % | 100% | ±0.9% |
Throughput over time
Median requests per second by date.
requests/s
22 Jul
GraphQL Federation specification
Apollo Federation v2
| Router | Run dates, versions and median requests per second |
|---|---|
| Apollo Gateway (Node 24) | 2026-07-22T11:52:09.000Z: 2.14.2, 265 requests/s, 2026-07-27T16:03:23.000Z: 2.14.3, 268 requests/s, 2026-07-30T16:01:56.000Z: 2.14.3, 266 requests/s, 2026-08-01T16:07:23.000Z: 2.14.3, 267 requests/s, 2026-08-05T16:56:21.000Z: 2.14.3, 270 requests/s, 2026-08-11T11:47:47.000Z: 2.14.3, 269 requests/s, 2026-08-20T16:40:29.000Z: 2.14.3, 268 requests/s, 2026-08-24T16:35:28.000Z: 2.14.3, 265 requests/s, 2026-08-27T17:26:23.000Z: 2.14.3, 265 requests/s, 2026-08-29T17:35:51.000Z: 2.14.3, 272 requests/s, 2026-08-31T16:39:02.000Z: 2.14.3, 267 requests/s, 2026-09-02T16:40:25.000Z: 2.14.3, 268 requests/s, 2026-09-09T16:36:14.000Z: 2.14.3, 265 requests/s, 2026-09-13T16:41:16.000Z: 2.14.3, 267 requests/s, 2026-09-17T16:37:09.000Z: 2.14.3, 270 requests/s, 2026-09-19T16:35:00.000Z: 2.14.3, 268 requests/s, 2026-09-22T16:40:03.000Z: 2.14.3, 258 requests/s, 2026-10-17T10:49:56.000Z: 2.14.4, 264 requests/s |
| Apollo Router 2.x (Rust) | 2026-07-22T11:52:09.000Z: 2.16.0, 422 requests/s, 2026-07-27T16:03:23.000Z: 2.16.1, 412 requests/s, 2026-07-30T16:01:56.000Z: 2.16.1, 407 requests/s, 2026-08-01T16:07:23.000Z: 2.16.1, 444 requests/s, 2026-08-05T16:56:21.000Z: 2.16.1, 445 requests/s, 2026-08-11T11:47:47.000Z: 2.16.1, 448 requests/s, 2026-08-20T16:40:29.000Z: 2.16.1, 405 requests/s, 2026-08-24T16:35:28.000Z: 2.16.1, 450 requests/s, 2026-08-27T17:26:23.000Z: 2.16.1, 447 requests/s, 2026-08-29T17:35:51.000Z: 2.16.1, 408 requests/s, 2026-08-31T16:39:02.000Z: 2.16.1, 450 requests/s, 2026-09-02T16:40:25.000Z: 2.16.1, 446 requests/s, 2026-09-09T16:36:14.000Z: 2.16.1, 410 requests/s, 2026-09-13T16:41:16.000Z: 2.16.1, 443 requests/s, 2026-09-17T16:37:09.000Z: 2.16.1, 441 requests/s, 2026-09-19T16:35:00.000Z: 2.16.1, 410 requests/s, 2026-09-22T16:40:03.000Z: 2.16.1, 449 requests/s, 2026-10-17T10:49:56.000Z: 2.18.0, 446 requests/s |
| Apollo Router 3.x (Rust) | 2026-10-16T10:24:10.000Z: 3.0.0-preview.0, 379 requests/s, 2026-10-17T10:49:56.000Z: 3.0.0-preview.0, 377 requests/s |
| Caliban (JVM 25) | 2026-10-16T10:24:10.000Z: 3.2.0, 1,454 requests/s, 2026-10-17T10:49:56.000Z: 3.2.0, 1,289 requests/s |
| Cosmo Router (Go) | 2026-07-22T11:52:09.000Z: 0.331.1, 1,187 requests/s, 2026-07-27T16:03:23.000Z: 0.334.0, 1,241 requests/s, 2026-07-30T16:01:56.000Z: 0.334.0, 1,225 requests/s, 2026-08-01T16:07:23.000Z: 0.334.0, 1,222 requests/s, 2026-08-05T16:56:21.000Z: 0.334.0, 1,231 requests/s, 2026-08-11T11:47:47.000Z: 0.334.0, 1,182 requests/s, 2026-08-20T16:40:29.000Z: 0.334.0, 1,190 requests/s, 2026-08-24T16:35:28.000Z: 0.334.0, 1,224 requests/s, 2026-08-27T17:26:23.000Z: 0.334.0, 1,237 requests/s, 2026-08-29T17:35:51.000Z: 0.334.0, 1,186 requests/s, 2026-08-31T16:39:02.000Z: 0.334.0, 1,228 requests/s, 2026-09-02T16:40:25.000Z: 0.334.0, 1,215 requests/s, 2026-09-09T16:36:14.000Z: 0.334.0, 1,230 requests/s, 2026-09-13T16:41:16.000Z: 0.334.0, 1,228 requests/s, 2026-09-17T16:37:09.000Z: 0.334.0, 1,182 requests/s, 2026-09-19T16:35:00.000Z: 0.334.0, 1,241 requests/s, 2026-09-22T16:40:03.000Z: 0.334.0, 1,226 requests/s, 2026-10-17T10:49:56.000Z: 0.359.0, 1,422 requests/s |
| Grafbase Gateway (Rust) | 2026-07-22T11:52:09.000Z: 0.53.5, 1,666 requests/s, 2026-07-27T16:03:23.000Z: 0.53.5, 1,619 requests/s, 2026-07-30T16:01:56.000Z: 0.53.5, 1,664 requests/s, 2026-08-01T16:07:23.000Z: 0.53.5, 1,684 requests/s, 2026-08-05T16:56:21.000Z: 0.53.5, 1,667 requests/s, 2026-08-11T11:47:47.000Z: 0.53.5, 1,587 requests/s, 2026-08-20T16:40:29.000Z: 0.53.5, 1,593 requests/s, 2026-08-24T16:35:28.000Z: 0.53.5, 1,680 requests/s, 2026-08-27T17:26:23.000Z: 0.53.5, 1,636 requests/s, 2026-08-29T17:35:51.000Z: 0.53.5, 1,673 requests/s, 2026-08-31T16:39:02.000Z: 0.53.5, 1,652 requests/s, 2026-09-02T16:40:25.000Z: 0.53.5, 1,626 requests/s, 2026-09-09T16:36:14.000Z: 0.53.5, 1,609 requests/s, 2026-09-13T16:41:16.000Z: 0.53.5, 1,645 requests/s, 2026-09-17T16:37:09.000Z: 0.53.5, 1,641 requests/s, 2026-09-19T16:35:00.000Z: 0.53.5, 1,629 requests/s, 2026-09-22T16:40:03.000Z: 0.53.5, 1,648 requests/s, 2026-10-17T10:49:56.000Z: 0.53.5, 1,679 requests/s |
| Hive Gateway (Node 24) | 2026-07-22T11:52:09.000Z: 2.10.4, 260 requests/s, 2026-07-27T16:03:23.000Z: 2.10.8, 262 requests/s, 2026-07-30T16:01:56.000Z: 2.10.8, 271 requests/s, 2026-08-01T16:07:23.000Z: 2.10.8, 260 requests/s, 2026-08-05T16:56:21.000Z: 2.10.8, 264 requests/s, 2026-08-11T11:47:47.000Z: 2.10.8, 271 requests/s, 2026-08-20T16:40:29.000Z: 2.10.8, 265 requests/s, 2026-08-24T16:35:28.000Z: 2.10.8, 266 requests/s, 2026-08-27T17:26:23.000Z: 2.10.8, 261 requests/s, 2026-08-29T17:35:51.000Z: 2.10.8, 270 requests/s, 2026-08-31T16:39:02.000Z: 2.10.8, 266 requests/s, 2026-09-02T16:40:25.000Z: 2.10.8, 257 requests/s, 2026-09-09T16:36:14.000Z: 2.10.8, 262 requests/s, 2026-09-13T16:41:16.000Z: 2.10.8, 263 requests/s, 2026-09-17T16:37:09.000Z: 2.10.8, 269 requests/s, 2026-09-19T16:35:00.000Z: 2.10.8, 264 requests/s, 2026-09-22T16:40:03.000Z: 2.10.8, 264 requests/s, 2026-10-17T10:49:56.000Z: 2.15.2, 261 requests/s |
| Hive Gateway · Router Runtime (Node 24) | 2026-07-22T11:52:09.000Z: 2.10.4, 580 requests/s, 2026-07-27T16:03:23.000Z: 2.10.8, 580 requests/s, 2026-07-30T16:01:56.000Z: 2.10.8, 596 requests/s, 2026-08-01T16:07:23.000Z: 2.10.8, 567 requests/s, 2026-08-05T16:56:21.000Z: 2.10.8, 590 requests/s, 2026-08-11T11:47:47.000Z: 2.10.8, 596 requests/s, 2026-08-20T16:40:29.000Z: 2.10.8, 573 requests/s, 2026-08-24T16:35:28.000Z: 2.10.8, 576 requests/s, 2026-08-27T17:26:23.000Z: 2.10.8, 593 requests/s, 2026-08-29T17:35:51.000Z: 2.10.8, 577 requests/s, 2026-08-31T16:39:02.000Z: 2.10.8, 571 requests/s, 2026-09-02T16:40:25.000Z: 2.10.8, 581 requests/s, 2026-09-09T16:36:14.000Z: 2.10.8, 570 requests/s, 2026-09-13T16:41:16.000Z: 2.10.8, 568 requests/s, 2026-09-17T16:37:09.000Z: 2.10.8, 578 requests/s, 2026-09-19T16:35:00.000Z: 2.10.8, 578 requests/s, 2026-09-22T16:40:03.000Z: 2.10.8, 589 requests/s, 2026-10-17T10:49:56.000Z: 2.15.2, 521 requests/s |
| Hive Router (Rust) | 2026-07-22T11:52:09.000Z: 0.0.83, 2,463 requests/s, 2026-07-27T16:03:23.000Z: 0.0.84, 2,411 requests/s, 2026-07-30T16:01:56.000Z: 0.0.84, 2,607 requests/s, 2026-08-01T16:07:23.000Z: 0.0.84, 2,572 requests/s, 2026-08-05T16:56:21.000Z: 0.0.84, 2,561 requests/s, 2026-08-11T11:47:47.000Z: 0.0.84, 2,485 requests/s, 2026-08-20T16:40:29.000Z: 0.0.84, 2,559 requests/s, 2026-08-24T16:35:28.000Z: 0.0.84, 2,417 requests/s, 2026-08-27T17:26:23.000Z: 0.0.84, 2,637 requests/s, 2026-08-29T17:35:51.000Z: 0.0.84, 2,467 requests/s, 2026-08-31T16:39:02.000Z: 0.0.84, 2,580 requests/s, 2026-09-02T16:40:25.000Z: 0.0.84, 2,424 requests/s, 2026-09-09T16:36:14.000Z: 0.0.84, 2,549 requests/s, 2026-09-13T16:41:16.000Z: 0.0.84, 2,348 requests/s, 2026-09-17T16:37:09.000Z: 0.0.84, 2,480 requests/s, 2026-09-19T16:35:00.000Z: 0.0.84, 2,412 requests/s, 2026-09-22T16:40:03.000Z: 0.0.84, 2,463 requests/s, 2026-10-17T10:49:56.000Z: 0.3.5, 2,523 requests/s |
| Fusion (.NET 10) | 2026-07-22T11:52:09.000Z: 16.5.1, 2,443 requests/s, 2026-07-27T16:03:23.000Z: 16.5.1, 2,320 requests/s, 2026-07-30T16:01:56.000Z: 16.5.1, 2,334 requests/s, 2026-08-01T16:07:23.000Z: 16.5.1, 2,398 requests/s, 2026-08-05T16:56:21.000Z: 16.5.1, 2,406 requests/s, 2026-08-11T11:47:47.000Z: 16.6.0, 2,379 requests/s, 2026-08-20T16:40:29.000Z: 16.6.1, 2,444 requests/s, 2026-08-24T16:35:28.000Z: 16.6.1, 2,492 requests/s, 2026-08-27T17:26:23.000Z: 16.6.1, 2,393 requests/s, 2026-08-29T17:35:51.000Z: 16.6.2, 2,394 requests/s, 2026-08-31T16:39:02.000Z: 16.6.2, 2,474 requests/s, 2026-09-02T16:40:25.000Z: 16.6.2, 2,394 requests/s, 2026-09-09T16:36:14.000Z: 16.6.4, 2,384 requests/s, 2026-09-13T16:41:16.000Z: 16.6.6, 2,399 requests/s, 2026-09-17T16:37:09.000Z: 16.6.6, 2,391 requests/s, 2026-09-19T16:35:00.000Z: 16.6.6, 2,385 requests/s, 2026-09-22T16:40:03.000Z: 16.6.6, 2,393 requests/s, 2026-10-17T10:49:56.000Z: 16.6.8, 2,398 requests/s |
| Fusion Nightly (.NET 10) | 2026-07-26T16:01:42.000Z: 16.6.0-p.3, 2,486 requests/s, 2026-07-29T16:13:06.000Z: 16.6.0-p.6, 2,368 requests/s, 2026-07-31T16:10:01.000Z: 16.6.0-p.8, 2,455 requests/s, 2026-08-03T16:01:43.000Z: 16.6.0-p.13, 2,462 requests/s, 2026-08-14T16:49:42.000Z: 16.6.1-p.2, 2,380 requests/s, 2026-08-23T16:36:55.000Z: 16.6.2-p.6, 2,472 requests/s, 2026-08-25T16:40:02.000Z: 16.6.2-p.7, 2,390 requests/s, 2026-08-28T19:36:23.000Z: 16.6.2-p.8, 2,457 requests/s, 2026-08-30T16:37:14.000Z: 16.7.0-p.1, 2,507 requests/s, 2026-08-31T16:39:02.000Z: 16.7.0-p.1, 2,463 requests/s, 2026-09-02T16:40:25.000Z: 16.7.0-p.2, 2,463 requests/s, 2026-09-09T16:36:14.000Z: 16.7.0-p.5, 2,464 requests/s, 2026-09-13T16:41:16.000Z: 16.7.0-p.6, 2,403 requests/s, 2026-09-17T16:37:09.000Z: 16.7.0-p.7, 2,429 requests/s, 2026-09-19T16:35:00.000Z: 16.7.0-p.8, 2,482 requests/s, 2026-09-22T16:40:03.000Z: 16.7.0-p.9, 2,361 requests/s, 2026-10-17T10:49:56.000Z: 16.7.0-p.28, 2,653 requests/s |
| Fusion Nightly (.NET 11) | 2026-07-26T16:01:42.000Z: 16.6.0-p.3, 2,533 requests/s, 2026-07-29T16:13:06.000Z: 16.6.0-p.6, 2,537 requests/s, 2026-07-31T16:10:01.000Z: 16.6.0-p.8, 2,427 requests/s, 2026-08-03T16:01:43.000Z: 16.6.0-p.13, 2,500 requests/s, 2026-08-14T16:49:42.000Z: 16.6.1-p.2, 2,518 requests/s, 2026-08-23T16:36:55.000Z: 16.6.2-p.6, 2,585 requests/s, 2026-08-25T16:40:02.000Z: 16.6.2-p.7, 2,475 requests/s, 2026-08-28T19:36:23.000Z: 16.6.2-p.8, 2,571 requests/s, 2026-08-30T16:37:14.000Z: 16.7.0-p.1, 2,574 requests/s, 2026-08-31T16:39:02.000Z: 16.7.0-p.1, 2,456 requests/s, 2026-09-02T16:40:25.000Z: 16.7.0-p.2, 2,468 requests/s, 2026-09-09T16:36:14.000Z: 16.7.0-p.5, 2,521 requests/s, 2026-09-13T16:41:16.000Z: 16.7.0-p.6, 2,509 requests/s, 2026-09-17T16:37:09.000Z: 16.7.0-p.7, 2,502 requests/s, 2026-09-19T16:35:00.000Z: 16.7.0-p.8, 2,540 requests/s, 2026-09-22T16:40:03.000Z: 16.7.0-p.9, 2,505 requests/s, 2026-10-17T10:49:56.000Z: 16.7.0-p.28, 2,652 requests/s |
| Fusion Nightly (.NET 10) | 2026-07-26T16:01:42.000Z: 16.6.0-p.3, 2,191 requests/s, 2026-07-29T16:13:06.000Z: 16.6.0-p.6, 2,202 requests/s, 2026-07-31T16:10:01.000Z: 16.6.0-p.8, 2,269 requests/s, 2026-08-03T16:01:43.000Z: 16.6.0-p.13, 2,186 requests/s, 2026-08-14T16:49:42.000Z: 16.6.1-p.2, 2,209 requests/s, 2026-08-23T16:36:55.000Z: 16.6.2-p.6, 2,317 requests/s, 2026-08-25T16:40:02.000Z: 16.6.2-p.7, 2,239 requests/s, 2026-08-28T19:36:23.000Z: 16.6.2-p.8, 2,214 requests/s, 2026-08-30T16:37:14.000Z: 16.7.0-p.1, 2,320 requests/s, 2026-08-31T16:39:02.000Z: 16.7.0-p.1, 2,332 requests/s, 2026-09-02T16:40:25.000Z: 16.7.0-p.2, 2,220 requests/s, 2026-09-09T16:36:14.000Z: 16.7.0-p.5, 2,295 requests/s, 2026-09-13T16:41:16.000Z: 16.7.0-p.6, 2,302 requests/s, 2026-09-17T16:37:09.000Z: 16.7.0-p.7, 2,215 requests/s, 2026-09-19T16:35:00.000Z: 16.7.0-p.8, 2,278 requests/s, 2026-09-22T16:40:03.000Z: 16.7.0-p.9, 2,210 requests/s, 2026-10-17T10:49:56.000Z: 16.7.0-p.28, 2,571 requests/s |
| feddi (JVM 25) | 2026-10-16T10:24:10.000Z: e91d605ed222, 934 requests/s, 2026-10-17T10:49:56.000Z: e91d605ed222, 1,131 requests/s |
Test conditions
Procedure
Every scenario runs these steps in order, one router at a time.
Start
The router runs on 2 dedicated physical cores (4 hardware threads). CPU boost is disabled to reduce clock-speed variation.
Warm up
One run of the full scenario length primes the router before anything is measured. Its results are discarded.
Measure
9 more runs of the same length follow. Each one sends the same GraphQL operation with the load profile of the scenario.
Check responses
A request only counts as a success when it returns HTTP 200 without GraphQL errors.
Report the median
Results use the median requests per second of the 9 runs, and run variance shows how much the runs differed.
Hardware
- Processor
- AMD Ryzen 7 5700G with Radeon Graphics
- CPU topology
- 8 physical cores (16 hardware threads, SMT).
- Memory
- 122 GB
Software
- Operating system
- Linux 6.8.0-147-generic
- Subgraphs
- Hot Chocolate 16.6.8 (.NET 10.0.13)
CPU pinning
- Hardware thread 0, physical core 0: OS & monitoring
- Hardware thread 8, physical core 0: OS & monitoring
- Hardware thread 1, physical core 1: Load generator
- Hardware thread 9, physical core 1: Load generator
- Hardware thread 2, physical core 2: Router
- Hardware thread 10, physical core 2: Router
- Hardware thread 3, physical core 3: Router
- Hardware thread 11, physical core 3: Router
- Hardware thread 4, physical core 4: Subgraphs
- Hardware thread 12, physical core 4: Subgraphs
- Hardware thread 5, physical core 5: Subgraphs
- Hardware thread 13, physical core 5: Subgraphs
- Hardware thread 6, physical core 6: Subgraphs
- Hardware thread 14, physical core 6: Subgraphs
- Hardware thread 7, physical core 7: Subgraphs
- Hardware thread 15, physical core 7: Subgraphs
- OS & monitoring
- Load generator
- Router
- Subgraphs
Processes are pinned with taskset; all other processes are moved onto core 0. Kernel threads and interrupts can still run on any core.
Published by ChilliCream, the team behind Fusion, using a harness based on The Guild's gateway benchmarks.