I’m trying to load test an API whose response exposes some additional custom metrics and attributes which aren’t fully controllable from the request side but are known to correlate with performance: Along the lines of internal cache hit/miss (boolean), retrieved intermediate values that affected the overall servicing time (scalar), etc.

I’m trying to load test an API whose response exposes some additional custom metrics and attributes which aren’t fully controllable from the request side but are known to correlate with performance: Along the lines of internal cache hit/miss (boolean), retrieved intermediate values that affected the overall servicing time (scalar), etc.

I’m trying to load test an API whose response exposes some additional custom metrics and attributes which aren’t fully controllable from the request side but are known to correlate with performance: Along the lines of internal cache hit/miss (boolean), retrieved intermediate values that affected the overall servicing time (scalar), etc.

locust -f locust_test.py –master-host=10.5.0.3 –master –master-port=8089 > master.log 2>&1 & for x in {1..7}; do locust -f locust_test.py –master-host=10.5.0.3 –master-port=8089 –worker > worker_$x.log 2>&1 & done

i have implemented single sign on from third party service and wants to do some custom logic inside locust stop test event hook with user details inside stop test event hook i am not able to fetch any object of flask session or current_user (https://flask-login.readthedocs.io/en/latest/) Setting the session object in init listener: @events.init.add_listener def locust_init(environment, […]

For context, I have a Locust task that issues an HTTP request that I want to time out if it doesn’t complete in N seconds. This differs from using the request timeout parameter since that only fails if no bytes are returned within a timeout.

Reading the locust manuals, there is an example on how to use locust as library here https://docs.locust.io/en/2.0.0/use-as-lib.html , I’m rewriting the code here for conveninece:

We are using Locust to run performance tests on our FastAPI endpoints on Google Cloud Platform. Intermittently, we encounter an issue that would not allow us to stop the test due to an error related to Greenlet/Gevent as soon as we click the “Stop” button. Locust will get stuck at the CleanUp stage while the requests are continue being sent.

I’m attempting to distribute a list of pre-defined request payloads across all the Users which are spawned in my run. Conceptually I want to split my list of N requests across U Users, such that each request is only issued once to the server.