Skip to content

docs: add benchmark navigation guidance #519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jeleel-muibi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add benchmark navigation guidance #519

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/contents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,22 @@
# Contents

## Finding Benchmark Assets

Many lesson folders include more than the short `README.md` next to the video link. Supporting files often live in sibling directories such as:

- `client/` or `tests/` for workload generators and benchmark clients
- `monitoring/`, Grafana dashboards, or Prometheus manifests for metrics and dashboards
- `terraform/`, `ansible/`, `docker-compose.yaml`, or deploy scripts for environment setup
- `app/`, `api/`, or `server/` directories for the application source code used in the lesson

Examples:

- [135 - How to monitor Containers in Kubernetes using Prometheus & cAdvisor?](../lessons/135) includes monitoring manifests and dashboards.
- [149 - gRPC vs REST performance benchmark](../lessons/149) includes `tests/`, `ansible/`, `terraform/`, and `monitoring/` assets.
- [228 - Redis vs Dragonfly Performance](../lessons/228) includes a `client/` implementation and monitoring manifests.

If you want to reproduce a lesson locally, start in the lesson directory and inspect the folders next to `README.md`. On GitHub, searching within a lesson for names like `client`, `tests`, `monitoring`, `terraform`, or `docker-compose` is usually the fastest way to find the relevant files.

- [069 - How to Create GKE Cluster Using TERRAFORM from Scratch?](../lessons/069)
- [070 - EKS Cluster Auto Scaling](../lessons/070)
- [071 - Kubernetes Horizontal Pod Autoscaler](../lessons/071)
Expand Down