From c30ae174ef93d5fc776c5681f80503a3cf754cc6 Mon Sep 17 00:00:00 2001
From: Damian Gryski <damian@gryski.com>
Date: Sun, 4 Mar 2018 10:59:04 -0800
Subject: [PATCH] add more load testing tooling

---
 performance.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/performance.md b/performance.md
index 973ece1..6a22470 100644
--- a/performance.md
+++ b/performance.md
@@ -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