locust 2.18.5.dev16__tar.gz → 2.18.5.dev32__tar.gz

{locust-2.18.5.dev16/locust.egg-info → locust-2.18.5.dev32}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: locust
-Version: 2.18.5.dev16
+Version: 2.18.5.dev32
 Summary: Developer friendly load testing framework
 License: MIT
 Project-URL: Homepage, https://locust.io/

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/changelog.rst

@@ -4,6 +4,12 @@ Changelog Highlights
 
 For full details of the Locust changelog, please see https://github.com/locustio/locust/blob/master/CHANGELOG.md
 
+2.19.0
+======
+* Add --processes parameter to automatically fork subprocesses for workers https://github.com/locustio/locust/pull/2472
+* Automatically shut down workers if master goes missing for too long https://github.com/locustio/locust/pull/2474
+* Update minimum version of various dependencies https://github.com/locustio/locust/pull/2476
+
 2.18.4
 ======
 * Various fixes to Modern UI

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/configuration.rst

@@ -59,7 +59,7 @@ Example:
     headless = true
     master = true
     expect-workers = 5
-    host = http://target-system
+    host = https://target-system
     users = 100
     spawn-rate = 10
     run-time = 10m
@@ -67,7 +67,7 @@ Example:
 
 .. code-block:: console
 
-    $ locust --config=master.conf
+    $ locust --config master.conf
 
 .. note::
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/retrieving-stats.rst

@@ -11,10 +11,10 @@ if you plan on running Locust in an automated way with the ``--headless`` flag:
 
 .. code-block:: console
 
-    $ locust -f examples/basic.py --csv=example --headless -t10m
+    $ locust -f examples/basic.py --csv example --headless -t10m
 
 The files will be named ``example_stats.csv``, ``example_failures.csv``, ``example_exceptions.csv`` and ``example_stats_history.csv``
-(when using ``--csv=example``). The first two files will contain the stats and failures for the whole 
+(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. The ``example_stats_history.csv`` 
 will get new rows with the *current* (10 seconds sliding window) stats appended during the whole test run. 
 By default only the Aggregate row is appended regularly to the history stats, but if Locust is started with 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/running-distributed.rst

@@ -10,70 +10,75 @@ But if your test plan is complex or you want to run even more load, you'll need
 
 To do this, you start one instance of Locust in master mode using the ``--master`` flag and multiple worker instances using the ``--worker`` flag. If the workers are not on the same machine as the master you use ``--master-host`` to point them to the IP/hostname of the machine running the master.
 
-The master instance runs Locust's web interface, and tells the workers when to spawn/stop Users. The workers run your Users and send back statistics to the master. The master instance doesn't run any Users itself.
+To make this easier, you can use the ``--processes`` flag to launch multiple instances. It will launch a master process and the specified number of worker processes. Used in combination with ``--worker`` it will only launch the workers.
+
+The master instance runs Locust's web interface, and tells the workers when to spawn/stop Users. The workers run your Users and send statistics back to the master. The master instance doesn't run any Users itself.
 
 Both the master and worker machines must have a copy of the locustfile when running Locust distributed.
 
 .. note::
-    Because Python cannot fully utilize more than one core per process (see `GIL <https://realpython.com/python-gil/>`_), you should typically run **one worker instance per processor core** on the worker machines in order to utilize all their computing power.
+    Because Python cannot fully utilize more than one core per process (see `GIL <https://realpython.com/python-gil/>`_), you will need to run **one worker instance per processor core** in order to have access to all your computing power.
 
 .. note::
     There is almost no limit to how many *Users* you can run per worker. Locust/gevent can run thousands or even tens of thousands of Users per process just fine, as long as their total request rate/RPS is not too high.
 
 .. note::
-    If Locust is getting close to running out of CPU resources, it will log a warning.
+    If Locust is getting close to running out of CPU resources, it will log a warning. If there is no warning, you can be pretty sure your test is not limited by load generator CPU.
 
-Example
-=======
+.. note::
+    ``--processes`` was introduced in Locust 2.19. Child processes are launched using fork which is not available in Windows.
 
-To start locust in master mode::
+Example 1: Everything on one machine
+====================================
 
-    locust -f my_locustfile.py --master
+It is really simple to launch a master and 4 worker processes::
 
-And then on each worker (replace ``192.168.0.14`` with the IP of the master machine, or leave out the parameter altogether if your workers are on the same machine as the master)::
+    locust --processes 4
 
-    locust -f my_locustfile.py --worker --master-host=192.168.0.14
+You can even auto-detect the number of cores in your machine and launch one worker for each of them::
 
+    locust --processes -1
 
-Options
-=======
+Example 2: Multiple machines
+============================
 
-``--master``
-------------
+Start locust in master mode on one machine::
 
-Sets locust in master mode. The web interface will run on this node.
+    locust -f my_locustfile.py --master
 
+And then on each worker machine::
 
-``--worker``
-------------
+    locust -f my_locustfile.py --worker --master-host <your master's address> --processes 4
 
-Sets locust in worker mode.
+Note that both master and worker nodes need access to the locustfile, it is not sent from master to worker automatically. But you can use `locust-swarm <https://github.com/SvenskaSpel/locust-swarm>`_ to automate that.
 
+Options
+=======
 
-``--master-host=X.X.X.X``
+``--master-host <hostname or ip>``
 -------------------------
 
 Optionally used together with ``--worker`` to set the hostname/IP of the master node (defaults
-to 127.0.0.1)
+to localhost)
 
-``--master-port=5557``
+``--master-port <port number>``
 ----------------------
 
 Optionally used together with ``--worker`` to set the port number of the master node (defaults to 5557).
 
-``--master-bind-host=X.X.X.X``
+``--master-bind-host <ip>``
 ------------------------------
 
 Optionally used together with ``--master``. Determines which network interface the master node
 will bind to. Defaults to * (all available interfaces).
 
-``--master-bind-port=5557``
+``--master-bind-port <port number>``
 ------------------------------
 
 Optionally used together with ``--master``. Determines what network ports that the master node will
 listen to. Defaults to 5557.
 
-``--expect-workers=X``
+``--expect-workers <number of workers>``
 ----------------------
 
 Used when starting the master node with ``--headless``. The master node will then wait until X worker

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/running-in-debugger.rst

@@ -47,7 +47,7 @@ Print HTTP communication
 
 Sometimes it can be hard to understand why an HTTP request fails in Locust when it works from a regular browser/other application. Here's how to examine the communication in detail:
 
-For ``HttpUser`` (`python-requests <http://python-requests.org>`_):
+For ``HttpUser`` (`python-requests <https://python-requests.org>`_):
 
 .. code-block:: python
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/testing-other-systems.rst

@@ -8,7 +8,7 @@ Locust only comes with built-in support for HTTP/HTTPS but it can be extended to
 
 .. note::
 
-    It is important that the protocol libraries you use can be `monkey-patched <http://www.gevent.org/intro.html#monkey-patching>`_ by gevent. 
+    It is important that the protocol libraries you use can be `monkey-patched <https://www.gevent.org/intro.html#monkey-patching>`_ by gevent. 
     
     Almost any libraries that are pure Python (using the Python ``socket`` module or some other standard library function like ``subprocess``) should work fine out of the box - but if they do their I/O calls in C, gevent will be unable to patch it. This will block the whole Locust/Python process (in practice limiting you to running a single User per worker process).
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/what-is-locust.rst

@@ -52,7 +52,7 @@ load against a dynamic website where most pages had different content for differ
 verbose configuration files to declare the tests. In Locust we took a different approach. Instead of configuration formats or UIs 
 you'd get a python framework that would let you define the behaviour of your users using Python code. 
 
-`Locust <http://en.wikipedia.org/wiki/Locust>`_ takes its name from the grasshopper species, known for their swarming behaviour. 
+`Locust <https://en.wikipedia.org/wiki/Locust>`_ takes its name from the grasshopper species, known for their swarming behaviour. 
 
 Previous versions of Locust used terminology borrowed from nature (swarming, hatching, attacking etc), but now employs more industry standard naming.
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/docs/writing-a-locustfile.rst

@@ -238,12 +238,10 @@ of request count independently of total user count.
 host attribute
 --------------
 
-The host attribute is a URL prefix (i.e. "http://google.com") to the host that is to be loaded.
-Usually, this is specified in Locust's web UI or on the command line, using the
-:code:`--host` option, when locust is started.
+The host attribute is a URL prefix (e.g. ``https://google.com``) to the host you want ot test. It is automatically added to requests, so you can do ``self.client.get("/")`` for example.
 
-If one declares a host attribute in the user class, it will be used in the case when no :code:`--host`
-is specified on the command line or in the web request.
+You can overwrite this value in Locust's web UI or on the command line, using the
+:code:`--host` option.
 
 tasks attribute
 ---------------

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/locust/_version.py

@@ -12,5 +12,5 @@ __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
 
-__version__ = version = '2.18.5.dev16'
-__version_tuple__ = version_tuple = (2, 18, 5, 'dev16')
+__version__ = version = '2.18.5.dev32'
+__version_tuple__ = version_tuple = (2, 18, 5, 'dev32')

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/locust/argument_parser.py

@@ -146,22 +146,32 @@ def get_empty_argument_parser(add_help=True, default_config_files=DEFAULT_CONFIG
         usage=configargparse.SUPPRESS,
         description=textwrap.dedent(
             """
-            Usage: locust [OPTIONS] [UserClass ...]
-
+Usage: locust [options] [UserClass ...]
         """
         ),
-        # epilog="",
+        epilog="""Examples:
+
+    locust -f my_test.py -H https://www.example.com
+
+    locust -u 100 -t 20m --headless --process 4 MyHttpUser AnotherUser
+
+See documentation for more details, including how to set options using a file or environment variables: https://docs.locust.io/en/stable/configuration.html""",
     )
     parser.add_argument(
         "-f",
         "--locustfile",
+        metavar="<filename>",
         default="locustfile",
-        help="Python module to import, e.g. '../other_test.py'. Either a .py file, multiple comma-separated .py files or a package "
-        "directory. Defaults to 'locustfile'.",
+        help="The Python file or module that contains your test, e.g. 'my_test.py'. Also accepts multiple comma-separated .py files or a package name/directory. Defaults to 'locustfile'.",
         env_var="LOCUST_LOCUSTFILE",
     )
 
-    parser.add_argument("--config", is_config_file_arg=True, help="Config file path")
+    parser.add_argument(
+        "--config",
+        is_config_file_arg=True,
+        help="File to read additional configuration from. See https://docs.locust.io/en/stable/configuration.html#configuration-file",
+        metavar="<filename>",
+    )
 
     return parser
 
@@ -251,13 +261,15 @@ def setup_parser_arguments(parser):
     parser.add_argument(
         "-H",
         "--host",
-        help="Host to load test in the following format: http://10.21.32.33",
+        metavar="<base url>",
+        help="Host to load test, in the following format: https://www.example.com",
         env_var="LOCUST_HOST",
     )
     parser.add_argument(
         "-u",
         "--users",
         type=int,
+        metavar="<int>",
         dest="num_users",
         help="Peak number of concurrent Locust users. Primarily used together with --headless or --autostart. Can be changed during a test by keyboard inputs w, W (spawn 1, 10 users) and s, S (stop 1, 10 users)",
         env_var="LOCUST_USERS",
@@ -266,12 +278,14 @@ def setup_parser_arguments(parser):
         "-r",
         "--spawn-rate",
         type=float,
+        metavar="<float>",
         help="Rate to spawn users at (users per second). Primarily used together with --headless or --autostart",
         env_var="LOCUST_SPAWN_RATE",
     )
     parser.add_argument(
         "--hatch-rate",
         env_var="LOCUST_HATCH_RATE",
+        metavar="<float>",
         type=float,
         default=0,
         help=configargparse.SUPPRESS,
@@ -279,6 +293,7 @@ def setup_parser_arguments(parser):
     parser.add_argument(
         "-t",
         "--run-time",
+        metavar="<time string>",
         help="Stop after the specified amount of time, e.g. (300s, 20m, 3h, 1h30m, etc.). Only used together with --headless or --autostart. Defaults to run forever.",
         env_var="LOCUST_RUN_TIME",
     )
@@ -294,6 +309,7 @@ def setup_parser_arguments(parser):
     web_ui_group.add_argument(
         "--web-host",
         default="",
+        metavar="<ip>",
         help="Host to bind the web interface to. Defaults to '*' (all interfaces)",
         env_var="LOCUST_WEB_HOST",
     )
@@ -301,6 +317,7 @@ def setup_parser_arguments(parser):
         "--web-port",
         "-P",
         type=int,
+        metavar="<port number>",
         default=8089,
         help="Port on which to run web host",
         env_var="LOCUST_WEB_PORT",
@@ -320,6 +337,7 @@ def setup_parser_arguments(parser):
     web_ui_group.add_argument(
         "--autoquit",
         type=int,
+        metavar="<seconds>",
         default=-1,
         help="Quits Locust entirely, X seconds after the run is finished. Only used together with --autostart. The default is to keep Locust running until you shut it down using CTRL+C",
         env_var="LOCUST_AUTOQUIT",
@@ -335,19 +353,22 @@ def setup_parser_arguments(parser):
         "--web-auth",
         type=str,
         dest="web_auth",
+        metavar="<username:password>",
         default=None,
-        help="Turn on Basic Auth for the web interface. Should be supplied in the following format: username:password",
+        help="DEPRECATED Turn on Basic Auth for the web interface. Should be supplied in the following format: username:password",
         env_var="LOCUST_WEB_AUTH",
     )
     web_ui_group.add_argument(
         "--tls-cert",
         default="",
+        metavar="<filename>",
         help="Optional path to TLS certificate to use to serve over HTTPS",
         env_var="LOCUST_TLS_CERT",
     )
     web_ui_group.add_argument(
         "--tls-key",
         default="",
+        metavar="<filename>",
         help="Optional path to TLS private key to use to serve over HTTPS",
         env_var="LOCUST_TLS_KEY",
     )
@@ -374,37 +395,40 @@ def setup_parser_arguments(parser):
     master_group.add_argument(
         "--master",
         action="store_true",
-        help="Set locust to run in distributed mode with this process as master",
+        help="Launch locust as a master node, to which worker nodes connect.",
         env_var="LOCUST_MODE_MASTER",
     )
     master_group.add_argument(
         "--master-bind-host",
         default="*",
-        help="Interfaces (hostname, ip) that locust master should bind to. Only used when running with --master. Defaults to * (all available interfaces).",
+        metavar="<ip>",
+        help="IP address for the master to listen on, e.g '192.168.1.1'. Defaults to * (all available interfaces).",
         env_var="LOCUST_MASTER_BIND_HOST",
     )
     master_group.add_argument(
         "--master-bind-port",
         type=int,
+        metavar="<port number>",
         default=5557,
-        help="Port that locust master should bind to. Only used when running with --master. Defaults to 5557.",
+        help="Port for the master to listen on. Defaults to 5557.",
         env_var="LOCUST_MASTER_BIND_PORT",
     )
     master_group.add_argument(
         "--expect-workers",
         type=int,
+        metavar="<int>",
         default=1,
-        help="How many workers master should expect to connect before starting the test (only when --headless/autostart is used).",
+        help="Delay starting the test until this number of workers have connected (only used in combination with --headless/--autostart).",
         env_var="LOCUST_EXPECT_WORKERS",
     )
     master_group.add_argument(
         "--expect-workers-max-wait",
         type=int,
+        metavar="<int>",
         default=0,
         help="How long should the master wait for workers to connect before giving up. Defaults to wait forever",
         env_var="LOCUST_EXPECT_WORKERS_MAX_WAIT",
     )
-
     master_group.add_argument(
         "--expect-slaves",
         action="store_true",
@@ -414,9 +438,8 @@ def setup_parser_arguments(parser):
     worker_group = parser.add_argument_group(
         "Worker options",
         """Options for running a Locust Worker node when running Locust distributed.
-Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, since other options such as -u, -r, -t are specified on the Master node.""",
+Typically ONLY these options (and --locustfile) need to be specified on workers, since other options (-u, -r, -t, ...) are controlled by the master node.""",
     )
-    # if locust should be run in distributed mode as worker
     worker_group.add_argument(
         "--worker",
         action="store_true",
@@ -426,7 +449,8 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
     worker_group.add_argument(
         "--processes",
         type=int,
-        help="Number of times to fork the locust process, to enable using multiple CPU cores. Use -1 to launch one process per CPU core in your system. Combine with --worker flag or let it automatically set --worker and --master flags for an all-in-one-solution. Not available on Windows. Experimental.",
+        metavar="<int>",
+        help="Number of times to fork the locust process, to enable using system. Combine with --worker flag or let it automatically set --worker and --master flags for an all-in-one-solution. Not available on Windows. Experimental.",
         env_var="LOCUST_PROCESSES",
     )
     worker_group.add_argument(
@@ -434,21 +458,20 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
         action="store_true",
         help=configargparse.SUPPRESS,
     )
-    # master host options
     worker_group.add_argument(
         "--master-host",
         default="127.0.0.1",
-        help="Host or IP address of locust master for distributed load testing. Only used when running with --worker. Defaults to 127.0.0.1.",
+        help="Hostname of locust master node to connect to. Defaults to 127.0.0.1.",
         env_var="LOCUST_MASTER_NODE_HOST",
-        metavar="MASTER_NODE_HOST",
+        metavar="<hostname>",
     )
     worker_group.add_argument(
         "--master-port",
         type=int,
+        metavar="<port number>",
         default=5557,
-        help="The port to connect to that is used by the locust master for distributed load testing. Only used when running with --worker. Defaults to 5557.",
+        help="Port to connect to on master node. Defaults to 5557.",
         env_var="LOCUST_MASTER_NODE_PORT",
-        metavar="MASTER_NODE_PORT",
     )
 
     tag_group = parser.add_argument_group(
@@ -459,7 +482,7 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
         "-T",
         "--tags",
         nargs="*",
-        metavar="TAG",
+        metavar="<tag>",
         env_var="LOCUST_TAGS",
         help="List of tags to include in the test, so only tasks with any matching tags will be executed",
     )
@@ -467,7 +490,7 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
         "-E",
         "--exclude-tags",
         nargs="*",
-        metavar="TAG",
+        metavar="<tag>",
         env_var="LOCUST_EXCLUDE_TAGS",
         help="List of tags to exclude from the test, so only tasks with no matching tags will be executed",
     )
@@ -476,6 +499,7 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
     stats_group.add_argument(
         "--csv",  # Name repeated in 'parse_options'
         dest="csv_prefix",
+        metavar="<string>",
         help="Store current request stats to files in CSV format. Setting this option will generate three files: [CSV_PREFIX]_stats.csv, [CSV_PREFIX]_stats_history.csv and [CSV_PREFIX]_failures.csv",
         env_var="LOCUST_CSV",
     )
@@ -507,6 +531,7 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
     )
     stats_group.add_argument(
         "--html",
+        metavar="<filename>",
         dest="html_file",
         help="Store HTML report to file path specified",
         env_var="LOCUST_HTML",
@@ -532,11 +557,13 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
         "-L",
         default="INFO",
         help="Choose between DEBUG/INFO/WARNING/ERROR/CRITICAL. Default is INFO.",
+        metavar="<level>",
         env_var="LOCUST_LOGLEVEL",
     )
     log_group.add_argument(
         "--logfile",
         help="Path to log file. If not set, log will go to stderr",
+        metavar="<filename>",
         env_var="LOCUST_LOGFILE",
     )
 
@@ -562,8 +589,9 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
     other_group.add_argument(
         "--exit-code-on-error",
         type=int,
+        metavar="<int>",
         default=1,
-        help="Sets the process exit code to use when a test result contain any failure or error",
+        help="Sets the process exit code to use when a test result contain any failure or error. Defaults to 1.",
         env_var="LOCUST_EXIT_CODE_ON_ERROR",
     )
     other_group.add_argument(
@@ -571,6 +599,7 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
         "--stop-timeout",
         action="store",
         dest="stop_timeout",
+        metavar="<number>",
         default="0",
         help="Number of seconds to wait for a simulated user to complete any executing task before exiting. Default is to terminate immediately. This parameter only needs to be specified for the master process when running Locust distributed.",
         env_var="LOCUST_STOP_TIMEOUT",
@@ -594,8 +623,8 @@ Only the LOCUSTFILE (-f option) needs to be specified when starting a Worker, si
     user_classes_group.add_argument(
         "user_classes",
         nargs="*",
-        metavar="UserClass",
-        help="Optionally specify which User classes that should be used (available User classes can be listed with -l or --list). LOCUST_USER_CLASSES environment variable can also be used to specify User classes",
+        metavar="<UserClass1 UserClass2>",
+        help="At the end of the command line, you can list User classes to be used (available User classes can be listed with --list). LOCUST_USER_CLASSES environment variable can also be used to specify User classes. Default is to use all available User classes",
         default=os.environ.get("LOCUST_USER_CLASSES", "").split(),
     )
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/locust/main.py

@@ -166,12 +166,21 @@ def main():
 
     if options.processes:
         if os.name == "nt":
-            raise Exception("--processes is not supported in Windows (except in WSL)")
+            sys.stderr.write("--processes is not supported in Windows (except in WSL)\n")
+            sys.exit(1)
         if options.processes == -1:
             options.processes = os.cpu_count()
-            assert options.processes, "couldnt detect number of cpus!?"
+            if not options.processes:
+                sys.stderr.write("--processes failed to detect number of cpus!?\n")
+                sys.exit(1)
         elif options.processes < -1:
-            raise Exception(f"invalid processes count {options.processes}")
+            sys.stderr.write(f"Invalid --processes count {options.processes}\n")
+            sys.exit(1)
+        elif options.master:
+            sys.stderr.write(
+                "--master cannot be combined with --processes. Remove --master, as it is implicit as long as --worker is not set.\n"
+            )
+            sys.exit(1)
         for _ in range(options.processes):
             child_pid = gevent.fork()
             if child_pid:

{locust-2.18.5.dev16 → locust-2.18.5.dev32}/locust/test/test_main.py

@@ -72,9 +72,9 @@ class StandaloneIntegrationTests(ProcessIntegrationTest):
             timeout=5,
             text=True,
         ).strip()
-        self.assertTrue(output.startswith("Usage: locust [OPTIONS] [UserClass ...]"))
+        self.assertTrue(output.startswith("Usage: locust [options] [UserClass"))
         self.assertIn("Common options:", output)
-        self.assertIn("-f LOCUSTFILE, --locustfile LOCUSTFILE", output)
+        self.assertIn("-f <filename>, --locustfile <filename>", output)
         self.assertIn("Logging options:", output)
         self.assertIn("--skip-log-setup      Disable Locust's logging setup.", output)
 

{locust-2.18.5.dev16 → locust-2.18.5.dev32/locust.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: locust
-Version: 2.18.5.dev16
+Version: 2.18.5.dev32
 Summary: Developer friendly load testing framework
 License: MIT
 Project-URL: Homepage, https://locust.io/