Algorithms/go-perfbook
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add more load testing tooling

Browse Source
This commit is contained in:
Damian Gryski 2018-03-04 10:59:04 -08:00
parent 87e785b45a
commit c30ae174ef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
performance.md
View File

@ -690,8 +690,8 @@ All optimizations should follow these steps:
are 'sufficiently' different for an optimization to be worth the added
code complexity.
1. use <https://github.com/tsenart/vegeta> for load testing http services
(+ other fancy ones)
1. make sure your latency numbers make sense:
(+ other fancy ones: k6, fortio, ...)
1. make sure your latency numbers make sense
The first step is important. It tells you when and where to start optimizing.
More importantly, it also tells you when to stop. Pretty much all optimizations