Add benchmark mention in CI

README.md

@@ -235,6 +235,7 @@ Using [GitHub actions](/actions) allows us to have an efficient CI/CD setup with
 | Workflow | Trigger | Purpose | Environment Variables |
 |----------|---------|---------|-----------------------|
 | **ci** | push | Continously test the build along with linting, formatting, best-practices (clippy), and validate deployment against LocalStack | |
+| **benchmark** | Pre-release using GitHub Releases | Run benchmark suite | **BENCHMARK_AWS_ACCESS_KEY_ID** <br /> **BENCHMARK_AWS_SECRET_ACCESS_KEY** <br /> **BENCHMARK_AWS_SECRET_ACCESS_KEY** |
 | **pre-release** | Pre-release using GitHub Releases | Deploy to a QA or staging environment |  **PRE_RELEASE_AWS_ACCESS_KEY_ID** <br /> **PRE_RELEASE_AWS_SECRET_ACCESS_KEY** <br /> **PRE_RELEASE_AWS_SECRET_ACCESS_KEY** |
 | **release** | Release using GitHub Releases | Deploy to production environment | **RELEASE_AWS_ACCESS_KEY_ID** <br /> **RELEASE_AWS_SECRET_ACCESS_KEY** <br /> **RELEASE_AWS_SECRET_ACCESS_KEY** |
 
@@ -265,6 +266,7 @@ Below are two charts generated by the benchmark, you can see the raw data in [th
 - 🟡: Fastest cold response time
 - 🟠: Slowest cold response time
 
+Benchmarks can be triggered in the CI by setting up its environment variables and creating a pre-release via GitHub Releases.
 
 ## 📚 Libraries
 We are using a couple of libraries, in various state of maturity/release: