Closed renovate[bot] closed 3 days ago
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 | 194 | 5933 total, 0 failed | avg: 337ms, p95: 789ms | ✅ |
apollo-router | 175 | 5327 total, 0 failed | avg: 482ms, p95: 728ms | ✅ |
wundergraph | 150 | 4588 total, 0 failed | avg: 549ms, p95: 1011ms | ✅ |
mesh-supergraph-bun | 78 | 2412 total, 0 failed | avg: 1227ms, p95: 2160ms | ✅ |
apollo-server | 53 | 1682 total, 0 failed | avg: 1816ms, p95: 2110ms | ✅ |
mercurius | 29 | 906 total, 0 failed | avg: 3353ms, p95: 4779ms | ✅ |
mesh-supergraph | 25 | 825 total, 0 failed | avg: 3737ms, p95: 6126ms | ✅ |
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 |
---|---|---|---|---|
cosmo | 182 | 5545 total, 0 failed | avg: 292ms, p95: 873ms | ✅ |
apollo-router | 171 | 5195 total, 0 failed | avg: 337ms, p95: 902ms | ✅ |
wundergraph | 155 | 4705 total, 0 failed | avg: 347ms, p95: 938ms | ✅ |
mesh-supergraph-bun | 85 | 2661 total, 0 failed | avg: 1114ms, p95: 1888ms | ✅ |
apollo-server | 73 | 2272 total, 0 failed | avg: 1333ms, p95: 1529ms | ✅ |
mesh-supergraph | 53 | 1671 total, 0 failed | avg: 1814ms, p95: 2671ms | ✅ |
mercurius | 47 | 1445 total, 0 failed | avg: 2088ms, p95: 2788ms | ✅ |
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 |
---|---|---|---|---|
cosmo | 191 | 5809 total, 0 failed | avg: 337ms, p95: 709ms | ✅ |
apollo-router | 171 | 5230 total, 0 failed | avg: 489ms, p95: 731ms | ✅ |
wundergraph | 153 | 4682 total, 0 failed | avg: 533ms, p95: 1021ms | ✅ |
mesh-supergraph-bun | 67 | 2076 total, 0 failed | avg: 1443ms, p95: 2509ms | ✅ |
apollo-server | 54 | 1703 total, 0 failed | avg: 1791ms, p95: 2329ms | ✅ |
mercurius | 29 | 933 total, 0 failed | avg: 3298ms, p95: 4280ms | ✅ |
mesh-supergraph | 24 | 779 total, 0 failed | avg: 3949ms, p95: 6414ms | ✅ |
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 |
---|---|---|---|---|---|
cosmo | 2250ms | 182 | 12797 total, 0 failed | avg: 748ms, p95: 2251ms, max: 9271ms, med: 501ms | ✅ |
wundergraph | 2422ms | 159 | 11175 total, 0 failed | avg: 865ms, p95: 2423ms, max: 7279ms, med: 675ms | ✅ |
apollo-router | 2847ms | 168 | 11793 total, 0 failed | avg: 861ms, p95: 2848ms, max: 9163ms, med: 551ms | ✅ |
mesh-supergraph-bun | 7823ms | 85 | 6013 total, 0 failed | avg: 3122ms, p95: 7824ms, max: 12433ms, med: 2861ms | ✅ |
mesh-supergraph | 8243ms | 55 | 3904 total, 0 failed | avg: 4948ms, p95: 8244ms, max: 10212ms, med: 5166ms | ✅ |
apollo-server | 22308ms | 71 | 5195 total, 0 failed | avg: 3994ms, p95: 22309ms, max: 44210ms, med: 2187ms | ✅ |
This PR contains the following updates:
3.0.0
->3.1.0
Release Notes
haltcase/tablemark (tablemark)
### [`v3.1.0`](https://togithub.com/haltcase/tablemark/blob/HEAD/changelog.md#310-2024-04-02) [Compare Source](https://togithub.com/haltcase/tablemark/compare/v3.0.0...v3.1.0) ###### FEATURES - support eliding padding in header separator ([#17](https://togithub.com/haltcase/tablemark/issues/17)) ([a4d24ce](https://togithub.com/haltcase/tablemark/commit/a4d24ce)), closes [#16](https://togithub.com/haltcase/tablemark/issues/16) ***Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.