chore(docs): Update load test description in the readme

README.md

@@ -22,17 +22,11 @@ Sea-ORM is being used to access database. PostgreSQL and MySQL are supported.
 
 A very brief load test is implemented in `loadtest` using `Goose` framework. It
 generates test load by first incrementally increasing requests up to the
-configure amount (defaults to amount of cpu cores), keeps the load for the
-configured amount of time measuring response latency.
-
-First brief results comparing python implementation (running under uwsgi) vs
-Rust implementation are present in the `loadtest/report_py.html` and
-`loadtest/report_rust.html`. It is absolutely clear that Rust implementation
-currently misses certain things original Keystone does (token validation is at
-the moment fake, policy evaluation is also missing, etc). In addition to that
-more reasonable test environment (comparable amount of python workers, etc,
-debug/release build) need to be established. However current test shows
-difference of factor **100** which is not going to be easy to beat.
+configured amount (defaults to count of the cpu cores), keeps the load for the
+configured amount of time while measuring the response latency and the throughput (RPS).
+
+For every PR load test suite is being executed. It is absolutely clear that the Rust implementation currently misses certain things original Keystone doe, but the gap is being closed over the time. However test shows
+difference of factor **10-100** which is already remarkable. New tests will appear to have a more thorough coverage of the exposed API.
 
 ## Trying