aws-samples / distributed-load-testing-with-locust-on-ecs Goto Github PK

Hello,

I am currently reviewing the Dockerfile in this repository and need some clarification regarding the commented-out code sections related to configuring Locust in different modes.

Specifically, I am trying to understand the implications of uncommenting the various lines for standalone, worker, and master modes. The current comments indicate that Locust is set up for standalone mode, but I am unclear about the exact meaning and implications of this setup.

Could you please provide more details on:

1. What the standalone mode entails in the context of this Dockerfile? Does it imply that only the master component is operational?
2. If uncommenting the worker or master sections is necessary, how would these changes affect the behavior of Locust? Would it mean that both master and worker operate as separate, unconnected instances?
3. In case I need to configure a distributed setup with both master and worker roles, what steps should I follow to ensure proper connectivity and coordination between these components?

I have included the relevant section of the Dockerfile for reference:

FROM --platform=linux/amd64 locustio/locust:2.8.3
COPY . ./

# for standalone
ENTRYPOINT ["locust", "-f", "./locustfile.py"]
# for worker
# CMD [ "--worker", "--master-host", "MASTER_HOST_NAME"]
# for master
# CMD ["--master"]

Any insights or guidance you can provide on this matter would be greatly appreciated.

Thank you for your time and assistance.

The current basic auth will be deprecated soon. We need to switch to the modern auth way: locustio/locust#2538

I executed npm ci without any issues. When I run npx cdk bootstrap I get the error below.

distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:513
return new TSError(diagnosticText, diagnosticCodes)
^
TSError: ⨯ Unable to compile TypeScript:
bin/load_test.ts:27:1 - error TS2304: Cannot find name 'n'.

27 n;
~

at createTSError (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:513:12)
at reportTSError (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:517:19)
at getOutput (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:752:36)
at Object.compile (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:968:32)
at Module.m._compile (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:1056:42)
at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Object.require.extensions.<computed> [as .ts] (C:\Users\nbrisard\GIT\distributed-load-testing-with-locust-on-ecs\node_modules\ts-node\src\index.ts:1059:12)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)

Using --web-auth WEB_AUTH option, we can enable basic authentication for Locust web UI.

c.f. https://docs.locust.io/en/stable/configuration.html