Skip to content

yorek/locust-on-azure

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 

Running Locust.io on Azure Container Instances

Running distributed Locust.io (version 1.3.0) on Azure Container Instances

Article with details is here:

Running Locust on Azure

Or just run azure-deploy.sh and follow instructions. Is that easy :)

A VNet integrated deployment is available via azure-vnet-deploy.sh

Locust on Azure

You can try it right away, even if you don't have any API you can call, using JSONPlaceholder. To avoid flooding JSONPlaceholder with tons of request, the default values are set to create 1 locust client that will simulate 1 user only. The user will send a GET or a POST request every 5 to 10 seconds.

Editing .sh files in VS Code on Windows

In case you are editing .sh files in Windows, you might encounter error at runtime in WSL because of the default CRLF line ending applied. You can fix existing files with command sed -i.bak 's/\r$//' azure-deploy.sh see this discussion and if you are using VS Code you can configure line ending

About

Running distributed Locust.io on Azure Container Instances

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published