Home

Awesome

GraphQL Benchmarks <!-- omit from toc -->

Open in GitHub Codespaces

Explore and compare the performance of the fastest GraphQL frameworks through our comprehensive benchmarks.

Introduction

This document presents a comparative analysis of several renowned GraphQL frameworks. Dive deep into the performance metrics, and get insights into their throughput and latency.

NOTE: This is a work in progress suite of benchmarks, and we would appreciate help from the community to add more frameworks or tune the existing ones for better performance.

Quick Start

Get started with the benchmarks:

  1. Click on this link to set up on GitHub Codespaces.
  2. Once set up in Codespaces, initiate the benchmark tests:
./setup.sh
./run_benchmarks.sh

Benchmark Results

<!-- PERFORMANCE_RESULTS_START -->
QueryServerRequests/secLatency (ms)Relative
1{ posts { id userId title user { id name email }}}
Tailcall20,544.404.85170.47x
GraphQL JIT1,107.9389.779.19x
async-graphql1,008.8898.398.37x
Caliban765.62130.246.35x
Gqlgen384.23256.393.19x
Netflix DGS190.52506.721.58x
Apollo GraphQL133.34691.401.11x
Hasura120.51736.921.00x
2{ posts { title }}
Tailcall32,700.503.0574.06x
async-graphql5,163.6219.4311.70x
Caliban4,797.8021.3610.87x
GraphQL JIT1,132.0288.162.56x
Gqlgen1,107.4998.862.51x
Apollo GraphQL894.83112.062.03x
Netflix DGS820.38122.481.86x
Hasura441.51229.881.00x
3{ greet }
Tailcall38,649.102.5822.59x
Caliban33,650.002.9819.66x
Gqlgen23,870.709.3513.95x
async-graphql23,703.504.2613.85x
GraphQL JIT4,460.0122.372.61x
Netflix DGS4,240.9028.062.48x
Apollo GraphQL4,084.5127.572.39x
Hasura1,711.2767.641.00x
<!-- PERFORMANCE_RESULTS_END -->

1. {posts {title body user {name}}}

Throughput (Higher is better)

Throughput Histogram

Latency (Lower is better)

Latency Histogram

2. {posts {title body}}

Throughput (Higher is better)

Throughput Histogram

Latency (Lower is better)

Latency Histogram

3. {greet}

Throughput (Higher is better)

Throughput Histogram

Latency (Lower is better)

Latency Histogram

Architecture

Architecture Diagram

A client (wrk) sends requests to a GraphQL server to fetch post titles. The GraphQL server, in turn, retrieves data from an external source, jsonplaceholder.typicode.com, routed through the nginx reverse proxy.

WRK

wrk serves as our test client, sending GraphQL requests at a high rate.

GraphQL

Our tested GraphQL server. We evaluated various implementations, ensuring no caching on the GraphQL server side.

Nginx

A reverse-proxy that caches every response, mitigating rate-limiting and reducing network uncertainties.

Jsonplaceholder

The primary upstream service forming the base for our GraphQL API. We query its /posts API via the GraphQL server.

GraphQL Schema

Inspect the generated GraphQL schema employed for the benchmarks:

schema {
  query: Query
}

type Query {
  posts: [Post]
}

type Post {
  id: Int!
  userId: Int!
  title: String!
  body: String!
  user: User
}

type User {
  id: Int!
  name: String!
  username: String!
  email: String!
  phone: String
  website: String
}

Contribute

Your insights are invaluable! Test these benchmarks, share feedback, or contribute by adding more GraphQL frameworks or refining existing ones. Open an issue or a pull request, and let's build a robust benchmarking resource together!