Contributions of additional benchmarks are welcome, provided they meet the following conditions:
There are near infinite combinations of web servers, interpreters, serializers and other configurations. We want to keep it simple, which means one benchmark per GraphQL implementation.
The choices to be made should be based on a mix of popularity and performance. Picking fasthttp over net/http in Go is acceptable because it is a well known and faster alternative, despite being less popular. But picking an experimental web server with virtually no adoption is not ok, even if it beats all others in performance.
We aim to compare benchmarks of GraphQL servers using default configurations because it reflects what most people see in production. Optimizations are permitted if they are prominently documented in their project's documentation.
Most server environments provide multiple processor cores, and implementations should be able to spread load among them.
Running benchmarks requires Crystal and Nix. A configuration for the VS Code remote containers extension is included in this repo.
- Create a folder with your benchmark files. Requests must be received as POST at
/graphqlon port 8000. - Add an entry to
benchmarks.yaml - Open a shell using
nix-shellto get all project dependencies - Run
./run.cr
To add new programming languages, update run.cr and shell.nix first.