You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide details how to containerize and run the `genMongoLoad` workload generator.
3
+
This guide details how to containerize and run the `plgm` workload generator.
4
4
5
5
Running the benchmark as a container inside your Kubernetes cluster is the **recommended approach** for performance testing. It bypasses local network proxies (VPNs, Ingress Controllers) and places the load generator on the same high-speed network fabric as the database, ensuring you measure database performance, not network latency.
6
6
@@ -17,13 +17,13 @@ Create a file named `Dockerfile` in the root of this project. We have provided a
17
17
Build the image locally.
18
18
19
19
```bash
20
-
docker build -t genmongoload:latest .
20
+
docker build -t plgm:latest .
21
21
```
22
22
23
23
> **Note for Kubernetes Users:** If your cluster is remote (EKS, GKE, AKS), you might have to tag and push this image to a registry your cluster can access:
24
24
> ```bash
25
-
> docker tag genmongoload:latest myregistry.azurecr.io/genmongoload:v1.0.0
A Kubernetes Job is the ideal choice for benchmarking as it runs to completion and then terminates. However, you may choose the deployment strategy that best fits your specific requirements.
34
34
35
-
### Create `genMongoLoad-job.yaml`
35
+
### Create `plgm-job.yaml`
36
36
37
-
We have provided a comprehensive sample manifest. It uses a Seed List for the URI (listing all three pods) to ensure high availability and utilizes the `GENMONGOLOAD_REPLICA_SET` variable among others to configure our options. This file is provided as an example; please edit [genMongoLoad-job.yaml](./genMongoLoad-job.yaml) to suit your specific requirements.
37
+
We have provided a comprehensive sample manifest. It uses a Seed List for the URI (listing all three pods) to ensure high availability and utilizes the `PERCONALOAD_REPLICA_SET` variable among others to configure our options. This file is provided as an example; please edit [plgm-job.yaml](./plgm-job.yaml) to suit your specific requirements.
38
38
39
39
### Execute the Benchmark
40
40
41
41
**1. Launch the Job**
42
42
```bash
43
-
kubectl apply -f genMongoLoad-job.yaml
44
-
job.batch/genmongoload created
43
+
kubectl apply -f plgm-job.yaml
44
+
job.batch/plgm created
45
45
```
46
46
47
47
**2. Watch the Output**
48
48
Find the pod created by the job and stream the logs to see the real-time "Ops/Sec" report.
0 commit comments