Closed renovate[bot] closed 4 months ago
federation-v1/constant-vus-subgraphs-delay
This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
This scenario was running 100 VUs over 30s
Gateway | RPS ⬇️ | Requests | Duration | Notes |
---|---|---|---|---|
apollo-router | 147 | 4513 total, 0 failed | avg: 618ms, p95: 795ms | ✅ |
wundergraph | 101 | 3138 total, 0 failed | avg: 940ms, p95: 1189ms | ✅ |
mesh-supergraph-bun | 88 | 2732 total, 0 failed | avg: 1082ms, p95: 1617ms | ✅ |
cosmo | 78 | 2443 total, 0 failed | avg: 1222ms, p95: 1465ms | ✅ |
apollo-server | 48 | 1524 total, 0 failed | avg: 2003ms, p95: 2393ms | ✅ |
mesh-supergraph | 29 | 933 total, 0 failed | avg: 3317ms, p95: 5173ms | ✅ |
mercurius | 12 | 455 total, 0 failed | avg: 7535ms, p95: 9038ms | ✅ |
federation-v1/constant-vus-over-time
This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
This scenario was running 100 VUs over 30s
Gateway | RPS ⬇️ | Requests | Duration | Notes |
---|---|---|---|---|
cosmo | 174 | 5301 total, 0 failed | avg: 510ms, p95: 677ms | ✅ |
apollo-router | 171 | 5218 total, 0 failed | avg: 514ms, p95: 697ms | ✅ |
wundergraph | 154 | 4691 total, 0 failed | avg: 534ms, p95: 953ms | ✅ |
mesh-supergraph-bun | 99 | 3059 total, 0 failed | avg: 973ms, p95: 1679ms | ✅ |
apollo-server | 50 | 1592 total, 0 failed | avg: 1917ms, p95: 2475ms | ✅ |
mercurius | 31 | 970 total, 0 failed | avg: 3130ms, p95: 4496ms | ✅ |
mesh-supergraph | 29 | 944 total, 0 failed | avg: 3300ms, p95: 5704ms | ✅ |
federation-v1/constant-vus-subgraphs-delay-resources
This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. It's being executed with a constant amount of VUs over a fixed amount of time. It measure things like memory usage, CPU usage, average RPS. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
This scenario was running 100 VUs over 30s
Gateway | RPS ⬇️ | Requests | Duration | Notes |
---|---|---|---|---|
apollo-router | 164 | 5032 total, 0 failed | avg: 536ms, p95: 726ms | ✅ |
wundergraph | 104 | 3236 total, 0 failed | avg: 909ms, p95: 1111ms | ✅ |
mesh-supergraph-bun | 102 | 3148 total, 0 failed | avg: 928ms, p95: 1323ms | ✅ |
cosmo | 83 | 2591 total, 0 failed | avg: 1144ms, p95: 1363ms | ✅ |
apollo-server | 63 | 1947 total, 0 failed | avg: 1547ms, p95: 1856ms | ✅ |
mesh-supergraph | 62 | 1951 total, 0 failed | avg: 1545ms, p95: 2223ms | ✅ |
mercurius | 12 | 475 total, 0 failed | avg: 7126ms, p95: 8328ms | ✅ |
federation-v1/ramping-vus
This scenario runs 4 subgraphs and a GraphQL gateway with Federation v1 spec, and runs a heavy query. We are running a heavy load of concurrent VUs to measure response time and other stats, during stress. It measure things like memory usage, CPU usage, response times. It also includes a summary of the entire execution, and metrics information about HTTP execution times.
This scenario was trying to reach 500 concurrent VUs over 60s
Gateway | duration(p95)⬇️ | RPS | Requests | Durations | Notes |
---|---|---|---|---|---|
wundergraph | 1871ms | 166 | 11633 total, 0 failed | avg: 685ms, p95: 1872ms, max: 4355ms, med: 523ms | ✅ |
cosmo | 2669ms | 172 | 12086 total, 0 failed | avg: 811ms, p95: 2670ms, max: 8943ms, med: 514ms | ✅ |
apollo-router | 2745ms | 173 | 12123 total, 0 failed | avg: 801ms, p95: 2746ms, max: 9840ms, med: 483ms | ✅ |
mesh-supergraph-bun | 5562ms | 118 | 8318 total, 0 failed | avg: 2208ms, p95: 5563ms, max: 8535ms, med: 2016ms | ✅ |
mesh-supergraph | 6714ms | 66 | 4648 total, 0 failed | avg: 4103ms, p95: 6715ms, max: 8278ms, med: 4288ms | ✅ |
apollo-server | 23637ms | 68 | 5024 total, 0 failed | avg: 4156ms, p95: 23637ms, max: 45152ms, med: 2227ms | ✅ |
This PR contains the following updates:
4.10.1
->4.10.2
Release Notes
apollographql/apollo-server (@apollo/server)
### [`v4.10.2`](https://togithub.com/apollographql/apollo-server/blob/HEAD/packages/server/CHANGELOG.md#4102) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/@apollo/server@4.10.1...@apollo/server@4.10.2) ##### Patch Changes - [#7849](https://togithub.com/apollographql/apollo-server/pull/7849) [`c7e514c`](https://togithub.com/apollographql/apollo-server/commit/c7e514cf67b05521c66d0561448b3c36b2facee6) Thanks [@TylerBloom](https://togithub.com/TylerBloom)! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.