Load testing Dapr
Before we activate a more complex test infrastructure for Locust on ACI, it is best to first check, and eventually debug, the Locust test locally.
The following steps take us through preparing the data to enabling autoscaling on a running load test:
- Preparing the data via port-forwarding
- Testing Locust locally
- Locust on ACI
- Configuring the HPA
First, we need to make sure the data in our environment can support our scenario. This is what we’ll do in the next section.
Preparing the data via port-forwarding
Before we launch the test, which is readily available at locust-on-azure\locust\locustfile.py, let’s focus on an aspect we oversaw; the SKU for the cookies is randomly composed from cookie001 to cookie999, with the addition of the infamous crazycookie, the main actor (pun intended) of the saga from Chapter 6, Publish and Subscribe.
The code that’s being used for our sample Dapr applications is extremely permissive...