The complete load testing platform. Everything you need for production-grade load tests. Serverless & distributed. Load test with Playwright. Load test HTTP APIs, GraphQL, WebSocket, and more. Use any Node.js module.
VERSION INFO:
Artillery: 2.0.11
Node.js: v18.20.1
OS: win32
Running this command:
.\node_modules\.bin\artillery run .\Test_ConsumeResourcesWithoutLogin.yml -o metrics.json
I expected to see this happen:
The test to terminate regardless of how overloaded the artillery process is or how many users fail over timing out.
Instead, this happened:
The test hangs indefinitely until it's forcefully terminated with 0 metrics being output on the console every 10s once all users complete the scenario. It also occurs when running the test through fargate. The cause of multiple timeouts in my situation was a specific endpoint returning a large json response body. Some of the real time endpoint metrics showed no high response times which led me to believe it's just client overload that can be resolved through horizontal scaling. A workaround so far has been to increase the http timeout and horizontally scale on more aws clusters.
Version info:
Running this command:
I expected to see this happen:
The test to terminate regardless of how overloaded the artillery process is or how many users fail over timing out.
Instead, this happened:
The test hangs indefinitely until it's forcefully terminated with 0 metrics being output on the console every 10s once all users complete the scenario. It also occurs when running the test through fargate. The cause of multiple timeouts in my situation was a specific endpoint returning a large json response body. Some of the real time endpoint metrics showed no high response times which led me to believe it's just client overload that can be resolved through horizontal scaling. A workaround so far has been to increase the http timeout and horizontally scale on more aws clusters.