New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enhancements to make this more valuable to GraphQL backend developers #3

Open

coco98 opened this issue Jun 5, 2018 · 2 comments

Contributor

coco98 commented Jun 5, 2018

Work your way up to a 95% percentile latency limit to automatically find the rps where the system breaks
Sample CPU and RAM (even if inaccurate) to give the developer a sense of resource consumption
Spin up and spin down a backend for every suite so that resources are freed up

Member

0x777 commented Aug 16, 2018

I agree.
We can't do this. There is no guarantee that the server that is being bench-marked is running on the same machine as graphql-bench.
We should have pre/post benchmarking scripts that can be executed

remorses commented Jun 4, 2020

You can take cpu and ram info from docker, there is a python docker api that can be used to get the container used resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment