Repository navigation
run-aci (Azure): arrivalCount not honoured for Playwright — local artillery run matches config, distributed run does not #3715
Michael-Robson
started this conversation in
Artillery
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We’re seeing different virtual-user behaviour between artillery run on a single machine and artillery run-aci on Azure when using the Playwright engine with the same TypeScript test script and phase settings.
Environment
Artillery: 2.0.30
Engine: Playwright (bundled)
Script: one Playwright scenario (login flow), single entry in scenarios
Phase (from env): e.g. duration 10–120s, arrivalCount 5–30, maxVusers set accordingly
Observed behaviour
Local (single process):
export ARTILLERY_DURATION=60
export ARTILLERY_ARRIVAL_COUNT=5
export ARTILLERY_MAX_VUSERS=5
pnpm exec artillery run artillery.authLoad.ts
Final summary: vusers.created: 5, vusers.completed: 5 — matches arrivalCount.
run-aci on Azure (examples):
Same script; same env vars passed to the worker process
--count (workers): e.g. 1, 3, or 6
From Artillery Cloud / the report:
arrivalCount: 10, maxVusers: 10, --count: 6 → vusers.created: 6 (not 10)
With --count: 1, we often see vusers.created: 1 even when arrivalCount is 5+
So vusers.created often tracks worker count rather than arrivalCount, which we do not see when running locally.
Questions
Thanks.
All reactions