add benchmark for response caching #1574
Conversation
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-mesh/fusion-runtime |
1.2.5-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway |
2.1.9-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/logger |
1.0.6-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/nestjs |
2.0.14-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/plugin-aws-sigv4 |
2.0.9-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/plugin-opentelemetry |
1.0.11-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/plugin-prometheus |
2.0.12-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway-runtime |
2.1.8-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/transport-common |
1.0.6-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/transport-http |
1.0.6-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/transport-http-callback |
1.0.6-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
@graphql-mesh/transport-ws |
2.0.6-alpha-f29abb07ca556b593bd55f8a4324e67665d784dc |
npm ↗︎ unpkg ↗︎ |
🚀 Snapshot Release (Binary for
|
🚀 Snapshot Release (Binary for
|
🚀 Snapshot Release (Binary for
|
🚀 Snapshot Release (Binary for
|
🚀 Snapshot Release (Binary for
|
🚀 Snapshot Release (Node Docker Image)The latest changes of this PR are available as image on GitHub Container Registry (based on the declared |
🚀 Snapshot Release (Bun Docker Image)The latest changes of this PR are available as image on GitHub Container Registry (based on the declared |
The response cache seems to have a pretty hight impact in the benchmark, but since subgraphs don't have much response latency, it should be less important in real use-cases.
Todo: