chore: bring back load testing with nixops #148
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just for manual bench tests for now, to ensure a change doesn't cause a performance regression.
Adds the following nixops commands to reproduce some bench tests:
Note: All of the nixops command need to run on the nix directory (
cd nix
).max requests for the nginx server:
It's capable of handling ~12k req/s.
reference bench test with the vegeta http client, only using one thread/worker:
Vegeta is able to do ~2.5K req/s.
With a pg_net.batch_size=32000, this uses pg_net for the bench test:
pg_net reaches 400 req/s max before request errors are reported. Like
Couldn't resolve host name
orCouldn't connect to server
. Doing 1000 req/s or higher results in a higher percentage of errors.These need further investigation, for now keeping the batch_size low is necessary for stability.