- Only p90 is being tested/shown - way to low.
- A custom simple thrown together client is being used - most likely doing CO(Coordinated Omission) - eg. results are incorrect/misleading
- One system is mostly tested in overload >100% cpu (due to 1&2 nothing is really measured before overload occurs eg. latency 0?! ), the test is quickly stopped once the Go test reaches overload.
- The tests are out of sync, one test gets ahead of the other, for a given time.
Remedy:
- Use p99, or better measure the distribution.
- Use a proper client like Gatling (it even has an easy to use/install javascript tool these days: https://docs.gatling.io/tutorials/test-as-code/javascript/running-your-first-simulation/)
- Keep going into overload, for both systems.
- Solved by 2 - using a proper client.
So it’s all about using a proper load testing tool/client.






















