Are you over 18 and want to see adult content?
More Annotations
A complete backup of https://cellphonetaskforce.org
Are you over 18 and want to see adult content?
A complete backup of https://yokeup.net
Are you over 18 and want to see adult content?
A complete backup of https://sirote.com
Are you over 18 and want to see adult content?
A complete backup of https://styledsnapshots.com
Are you over 18 and want to see adult content?
A complete backup of https://zealllc.com
Are you over 18 and want to see adult content?
A complete backup of https://ufonts.com
Are you over 18 and want to see adult content?
A complete backup of https://townofbethanybeach.com
Are you over 18 and want to see adult content?
A complete backup of https://www.gov.gs
Are you over 18 and want to see adult content?
A complete backup of https://blender.com
Are you over 18 and want to see adult content?
A complete backup of https://majestickl.com
Are you over 18 and want to see adult content?
A complete backup of https://nobonusaffiliates.com
Are you over 18 and want to see adult content?
A complete backup of https://hipaajournal.com
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of yiiframework.com
Are you over 18 and want to see adult content?
A complete backup of spiaggiabonetti.it
Are you over 18 and want to see adult content?
A complete backup of orgprepdaily.wordpress.com
Are you over 18 and want to see adult content?
A complete backup of ragnarok222.tumblr.com
Are you over 18 and want to see adult content?
A complete backup of fernwoodcabin.com
Are you over 18 and want to see adult content?
A complete backup of mcclintockip.com
Are you over 18 and want to see adult content?
Text
class at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST - A MODERN LOAD TESTING FRAMEWORKDOCUMENTATIONTESTING OTHER SYSTEMS USING CUSTOMWHAT IS LOCUSTINSTALLATIONQUICK START An open source load testing tool. Define user behaviour in code. No need for clunky UIs or bloated XML. Just plain code. Distributed & scalable. Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users. Proven & battle tested. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.com API — LOCUST 1.5.3 DOCUMENTATION Response class ¶. This class actually resides in the python-requests library, since that’s what Locust is using to make HTTP requests, but it’s included in the API docs for locust since it’s so central when writing locust load tests. You can also look at the Responseclass at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.comWHAT IS LOCUST?
Locust makes it easy to run load tests distributed over multiple machines. It is event-based (using gevent), which makes it possible for a single process to handle many thousands concurrent users.While there may be other tools that are capable of doing more requests per second on a given hardware, the low overhead of each Locust user makes it very suitable for testing highly concurrent workloads.QUICK START
Here we define a class for the users that we will be simulating. It inherits from HttpUser which gives each user a client attribute, which is an instance of HttpSession, that can be used to make HTTP requests to the target system that we want to load test.When a test starts, locust will create an instance of this class for every user that it simulates, and each of these users will start TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. DEVELOPING LOCUST ITSELF Build documentation¶. To build the documentation you first need to install the required PyPI packages. You can do that by running the following command in the Locust project’s root directory: RUNNING LOCUST DISTRIBUTED Running Locust distributed. Once a single machine isn’t enough to simulate the number of users that you need, Locust supports running load tests distributed across multiple machines. To do this, you start one instance of Locust in master mode using the --master flag. This is the instance that will be running Locust’s web interface where you RUNNING LOCUST WITHOUT THE WEB UI Running Locust distributed without the web UI¶. If you want to run Locust distributed without the web UI, you should specify the --expect-workers option when starting the master node, to specify the number of worker nodes that are expected to connect. It will then wait until that many worker nodes have connected before starting the test. WRITING A LOCUSTFILE The tasks attribute¶. As stated above, the tasks attribute defines the different tasks a locust user will perform. If the tasks attribute is specified as a list, each time a task is to be performed, it will be randomly chosen from the tasks attribute. If however, tasks is a dict - with callables as keys and ints as values - the task that is to be executed will be chosen at random but with the RETRIEVE TEST STATISTICS IN CSV FORMAT The files will be named example_stats.csv, example_failures.csv and example_history.csv (when using --csv=example).The first two files will contain the stats and failures for the whole test run, with a row for every stats entry (URL endpoint) and an aggregated row. INCREASE LOCUST’S PERFORMANCE WITH A FASTER HTTP CLIENT Increase Locust’s performance with a faster HTTP client¶. Locust’s default HTTP client uses python-requests.The reason for this is that requests is a very well-maintained python package, that provides a really nice API, that many python developers are familiarwith.
LOCUST - A MODERN LOAD TESTING FRAMEWORKDOCUMENTATIONTESTING OTHER SYSTEMS USING CUSTOMWHAT IS LOCUSTINSTALLATIONQUICK START An open source load testing tool. Define user behaviour in code. No need for clunky UIs or bloated XML. Just plain code. Distributed & scalable. Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users. Proven & battle tested. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.com API — LOCUST 1.5.3 DOCUMENTATION Response class ¶. This class actually resides in the python-requests library, since that’s what Locust is using to make HTTP requests, but it’s included in the API docs for locust since it’s so central when writing locust load tests. You can also look at the Responseclass at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST - A MODERN LOAD TESTING FRAMEWORKDOCUMENTATIONTESTING OTHER SYSTEMS USING CUSTOMWHAT IS LOCUSTINSTALLATIONQUICK START An open source load testing tool. Define user behaviour in code. No need for clunky UIs or bloated XML. Just plain code. Distributed & scalable. Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users. Proven & battle tested. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.com API — LOCUST 1.5.3 DOCUMENTATION Response class ¶. This class actually resides in the python-requests library, since that’s what Locust is using to make HTTP requests, but it’s included in the API docs for locust since it’s so central when writing locust load tests. You can also look at the Responseclass at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.comWHAT IS LOCUST?
Locust makes it easy to run load tests distributed over multiple machines. It is event-based (using gevent), which makes it possible for a single process to handle many thousands concurrent users.While there may be other tools that are capable of doing more requests per second on a given hardware, the low overhead of each Locust user makes it very suitable for testing highly concurrent workloads.QUICK START
Here we define a class for the users that we will be simulating. It inherits from HttpUser which gives each user a client attribute, which is an instance of HttpSession, that can be used to make HTTP requests to the target system that we want to load test.When a test starts, locust will create an instance of this class for every user that it simulates, and each of these users will start TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. RUNNING LOCUST WITHOUT THE WEB UI Running Locust distributed without the web UI¶. If you want to run Locust distributed without the web UI, you should specify the --expect-workers option when starting the master node, to specify the number of worker nodes that are expected to connect. It will then wait until that many worker nodes have connected before starting the test.TASKSET CLASS
Tags and TaskSets ¶. You can tag TaskSets using the @tag decorator in a similar way to normal tasks, but there are some nuances worth mentioning. Tagging a TaskSet will automatically apply the tag (s) to all of the TaskSet’s tasks. Furthermore, if you tag a task within a nested TaskSet, Locust will execute that task even if the TaskSet isn RUNNING LOCUST DISTRIBUTED Running Locust distributed. Once a single machine isn’t enough to simulate the number of users that you need, Locust supports running load tests distributed across multiple machines. To do this, you start one instance of Locust in master mode using the --master flag. This is the instance that will be running Locust’s web interface where you WRITING A LOCUSTFILE The tasks attribute¶. As stated above, the tasks attribute defines the different tasks a locust user will perform. If the tasks attribute is specified as a list, each time a task is to be performed, it will be randomly chosen from the tasks attribute. If however, tasks is a dict - with callables as keys and ints as values - the task that is to be executed will be chosen at random but with the RETRIEVE TEST STATISTICS IN CSV FORMAT The files will be named example_stats.csv, example_failures.csv and example_history.csv (when using --csv=example).The first two files will contain the stats and failures for the whole test run, with a row for every stats entry (URL endpoint) and an aggregated row. INCREASE LOCUST’S PERFORMANCE WITH A FASTER HTTP CLIENT Increase Locust’s performance with a faster HTTP client¶. Locust’s default HTTP client uses python-requests.The reason for this is that requests is a very well-maintained python package, that provides a really nice API, that many python developers are familiarwith.
LOCUST - A MODERN LOAD TESTING FRAMEWORKDOCUMENTATIONTESTING OTHER SYSTEMS USING CUSTOMWHAT IS LOCUSTINSTALLATIONQUICK START An open source load testing tool. Define user behaviour in code. No need for clunky UIs or bloated XML. Just plain code. Distributed & scalable. Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users. Proven & battle tested. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.com API — LOCUST 1.5.3 DOCUMENTATION Response class ¶. This class actually resides in the python-requests library, since that’s what Locust is using to make HTTP requests, but it’s included in the API docs for locust since it’s so central when writing locust load tests. You can also look at the Responseclass at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST - A MODERN LOAD TESTING FRAMEWORKDOCUMENTATIONTESTING OTHER SYSTEMS USING CUSTOMWHAT IS LOCUSTINSTALLATIONQUICK START An open source load testing tool. Define user behaviour in code. No need for clunky UIs or bloated XML. Just plain code. Distributed & scalable. Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users. Proven & battle tested. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.com API — LOCUST 1.5.3 DOCUMENTATION Response class ¶. This class actually resides in the python-requests library, since that’s what Locust is using to make HTTP requests, but it’s included in the API docs for locust since it’s so central when writing locust load tests. You can also look at the Responseclass at
INSTALLATION
Installation ¶. Installation. Install Python 3.6 or later. Install Locust using pip. $ pip3 install locust. Validate your installation and show the Locust version number: $ locust -V. If everything worked, move on to Quick start. If it did not, check out the wiki for somesolutions.
CONFIGURATION
The most straight forward way to Configure how Locust is run is through command line arguments. Usage: locust Common options: -h, --help show this help message and exit -f LOCUSTFILE, --locustfile LOCUSTFILE Python module file to import, e.g.'../other.py'.
USING LOCUST AS A LIBRARY Using Locust as a library. It’s possible to use Locust as a library, instead of running Locust using the locust command. To run Locust as a library you need to create an Environment instance: from locust.env import Environment env = Environment(user_classes=) The Environment instance’s create_local_runner , create_master_runner RUNNING LOCUST WITH DOCKER Running Locust with Docker¶. The official Docker image is currently found at locustio/locust.. The docker image can be used like this (assuming that the locustfile.py exists in the current workingdirectory):
WRITING A LOCUSTFILE If you started this test with --tags tag1, only task1 and task2 would be executed during the test. If you started it with --tags tag2 tag3, only task2 and task3 would be executed.--exclude-tags will behave in the exact opposite way. So, if you start the test with --exclude-tags tag3, only task1, task2, and task4 will be executed. Exclusion always wins over inclusion, so if a task has a tag you TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. GENERATING A CUSTOM LOAD SHAPE Generating a custom load shape¶. Sometimes a completely custom shaped load test is required that cannot be achieved by simply setting or changing the user count and spawn rate. LOCUST DOCUMENTATION Locust Documentation¶. About locust. Locust is a scalable load testing framework written in Python. Website: https://locust.io/. Source code: https://github.comWHAT IS LOCUST?
Locust makes it easy to run load tests distributed over multiple machines. It is event-based (using gevent), which makes it possible for a single process to handle many thousands concurrent users.While there may be other tools that are capable of doing more requests per second on a given hardware, the low overhead of each Locust user makes it very suitable for testing highly concurrent workloads.QUICK START
Here we define a class for the users that we will be simulating. It inherits from HttpUser which gives each user a client attribute, which is an instance of HttpSession, that can be used to make HTTP requests to the target system that we want to load test.When a test starts, locust will create an instance of this class for every user that it simulates, and each of these users will start TESTING OTHER SYSTEMS USING CUSTOM CLIENTS Testing other systems using custom clients ¶. Testing other systems using custom clients. Locust was built with HTTP as its main use case but it can be extended to load test almost any system. You do this by writing a custom client that triggers request. RUNNING LOCUST WITHOUT THE WEB UI Running Locust distributed without the web UI¶. If you want to run Locust distributed without the web UI, you should specify the --expect-workers option when starting the master node, to specify the number of worker nodes that are expected to connect. It will then wait until that many worker nodes have connected before starting the test.TASKSET CLASS
Tags and TaskSets ¶. You can tag TaskSets using the @tag decorator in a similar way to normal tasks, but there are some nuances worth mentioning. Tagging a TaskSet will automatically apply the tag (s) to all of the TaskSet’s tasks. Furthermore, if you tag a task within a nested TaskSet, Locust will execute that task even if the TaskSet isn RUNNING LOCUST DISTRIBUTED Running Locust distributed. Once a single machine isn’t enough to simulate the number of users that you need, Locust supports running load tests distributed across multiple machines. To do this, you start one instance of Locust in master mode using the --master flag. This is the instance that will be running Locust’s web interface where you WRITING A LOCUSTFILE The tasks attribute¶. As stated above, the tasks attribute defines the different tasks a locust user will perform. If the tasks attribute is specified as a list, each time a task is to be performed, it will be randomly chosen from the tasks attribute. If however, tasks is a dict - with callables as keys and ints as values - the task that is to be executed will be chosen at random but with the RETRIEVE TEST STATISTICS IN CSV FORMAT The files will be named example_stats.csv, example_failures.csv and example_history.csv (when using --csv=example).The first two files will contain the stats and failures for the whole test run, with a row for every stats entry (URL endpoint) and an aggregated row. INCREASE LOCUST’S PERFORMANCE WITH A FASTER HTTP CLIENT Increase Locust’s performance with a faster HTTP client¶. Locust’s default HTTP client uses python-requests.The reason for this is that requests is a very well-maintained python package, that provides a really nice API, that many python developers are familiarwith.
Locust
* Documentation
* Code
------------------------- AN OPEN SOURCE LOAD TESTING TOOL. Define user behaviour with Python code, and swarm your system with millions of simultaneous users.*
*
*
DEFINE USER BEHAVIOUR IN CODE No need for clunky UIs or bloated XML. Just plain code. __*
DISTRIBUTED & SCALABLE Locust supports running load tests distributed over multiple machines, and can therefore be used to simulate millions of simultaneous users __*
PROVEN & BATTLE TESTED Locust has been used to simulate millions of simultaneous users. Battlelog, the web app for the Battlefield games, is load tested using Locust, so one can really say Locust is Battletested ;). __ > I'm impressed not more people talk about locust (http://locust.io/). > The thing is awesome :) Shoutout too the guys from ESN :)> Armin
> Ronacher @mitsuhiko > Author of Flask, Jinja2 & more > it’s become a mandatory part of the development of any large scale > HTTP service built at DICE at this point.> Joakim
> Bodin @jbripley > Lead Software Engineer at EA/DICE > locust.io is pretty fantastic, wish it had a bit more in the way of > docs for non-HTTP stuff though> Alex
> Gaynor @alex_gaynor > Django & PyPy core developer ______ locustfile.py from locust import HttpUser, between, task class WebsiteUser(HttpUser): wait_time = between(5, 15) def on_start(self): self.client.post("/login", { "username": "test_user","password": ""
})
@task
def index(self):
self.client.get("/") self.client.get("/static/assets.js")@task
def about(self):
self.client.get("/about/") # This locust test script example will simulate a user # browsing the Locust documentation on https://docs.locust.ioimport random
from locust import HttpUser, between, task from pyquery import PyQuery class AwesomeUser(HttpUser): host = "https://docs.locust.io/en/latest/" # we assume someone who is browsing the Locust docs, # generally has a quite long waiting time (between # 10 and 600 seconds), since there's a bunch of text# on each page
wait_time = between(10, 600) def on_start(self): # start by waiting so that the simulated users # won't all arrive at the same timeself.wait()
# assume all users arrive at the index pageself.index_page()
self.urls_on_current_page = self.toc_urls@task(10)
def index_page(self): r = self.client.get("") pq = PyQuery(r.content) link_elements = pq(".toctree-wrapper a.internal")self.toc_urls =
@task(50)
def load_page(self): url = random.choice(self.toc_urls) r = self.client.get(url) pq = PyQuery(r.content) link_elements = pq("a.internal") self.urls_on_current_page =@task(30)
def load_sub_page(self): url = random.choice(self.urls_on_current_page) r = self.client.get(url) # An example on how to use and nest TaskSets from locust import HttpUser, TaskSet, task, between class ForumThread(TaskSet):pass
class ForumPage(TaskSet): # wait_time can be overridden for individual TaskSets wait_time = between(10, 300) # TaskSets can be nested multiple levelstasks = {
ForumThread:3
}
@task(3)
def forum_index(self):pass
@task(1)
def stop(self):
self.interrupt()
class AboutPage(TaskSet):pass
class WebsiteUser(HttpUser): wait_time = between(5, 15) # We can specify sub TaskSets using the tasks dicttasks = {
ForumPage: 20,
AboutPage: 10,
}
# We can use the @task decorator as well as the # tasks dict in the same Locust/TaskSet@task(10)
def index(self):
pass
$ locust -f locustfile.pyEXAMPLE CODE
A fundamental feature of Locust is that you describe all your test in Python code. No need for clunky UIs or bloated XML, just plain code.SELECT EXAMPLE __
* SIMPLE
* WITH HTML PARSING
* NESTED TASKSETS
-------------------------USED BY
*
*
*
*
*
*
*
*
*
*
*
*
INSTALLATION
The easiest way to install Locust is from PyPI, using pip
:
_>_ pip install locust __ Read more detailed installations instructions in the documentation.
__ Get the source code at Github . MAINTAINERS & CONTRIBUTORS*
Jonatan Heyman
@jonatanheyman
*
Corey Goldberg
@cgoldberg
*
Peter Darrow
@pmdarrow
*
Justin Iso
@JustinIso
*
Alden Peterson
*
Mark Beacom
@mbeacom
*
Lars Holmberg
@cyberw
-------------------------*
HeyHugo
*
Trouv
*
cgbystrom
*
Jahaja
*
delulu
*
jdufresne
*
DeepHorizons
*
anuj-ssharma
*
PayscaleNateW
*
ajt89
*
ronniekk
*
alercunha
*
sanga
*
mehta-ankit
*
myzhan
And more than 100
additional
awesome contributors!
ORIGINAL AUTHORS
*
Jonatan Heyman
@jonatanheyman
*
Carl Byström
@cgbystrom
*
Joakim Hamrén
@jahaaja
*
Hugo Heyman
@hugoheyman
-------------------------*
*
Details
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0