improved benchmark situation in readme

README.md

@@ -122,9 +122,14 @@ integrate.
 @alexpyattaev, the benchmarks are fairer now, pinning server and client to
 specific CPU cores.
 
-![](./wrk/samples/req_per_sec_graph.png)
+**Update**: I have consolidated the benchmarks to one good representative per
+language. See more details in [blazingly-fast.md](./blazingly-fast.md). It
+contains rust implementations that come pretty close to zap's performance in the
+simplistic testing scenario.
 
-![](./wrk/samples/xfer_per_sec_graph.png)
+![](./wrk/samples/README_req_per_sec.png)
+
+![](./wrk/samples/README_xfer_per_sec.png)
 
 
 So, being somewhere in the ballpark of basic GO performance, zig zap seems to be

blazingly-fast.md

@@ -169,7 +169,7 @@ Vulnerabilities:
   Tsx async abort:       Not affected
 ```
 
-### Workstation at work
+### Workstation at work -- out of date (fixed soon)
 
 A beast. Many cores (which we don't use). 
 
@@ -247,7 +247,7 @@ Vulnerabilities:
 ```
 
 
-### Work Laptop
+### Work Laptop -- out of date (fixed soon)
 
 Very strange. It absolutely **LOVES** zap 🤣!
 

wrk/measure_all.sh

@@ -8,6 +8,11 @@ fi
 
 SUBJECTS="$1"
 
+if [ "$SUBJECTS" = "README" ] ; then 
+    rm -f wrk/*.perflog
+    SUBJECTS="zig-zap go python-sanic rust-axum csharp cpp-beast"
+fi
+
 if [ -z "$SUBJECTS" ] ; then
     SUBJECTS="zig-zap go python python-sanic rust-bythebook rust-bythebook-improved rust-clean rust-axum csharp cpp-beast"
 fi