.. index:: options
.. _sec-options-label:
Setting options
===============
.. index:: override
.. index:: thinktime
.. index:: ssl_ciphers
.. index:: ssl_versions
.. index:: ssl_reuse_sessions
.. index:: tcp_snd_buffer
.. index:: tcp_rcv_buffer
.. index:: udp_snd_buffer
.. index:: udp_rcv_buffer
.. index:: max_ssh_startup
Thinktimes, SSL, Buffers
------------------------
Default values can be set-up globally: ``thinktime`` between requests
in the scenario, SSL cipher algorithms (use ssl:cipher_suites(openssl). to get a
list of available ciphers), TCP/UDP buffer sizes (the default value is 32KB).
These values overrides those set in session configuration tags if override is true.
.. code-block:: xml
.. versionadded:: 1.6.0
You can disable the SSL session cache (it is enabled by default)
.. code-block:: xml
You can specify which SSL protocol you want use. Use ssl:versions(). to get
a list of available ssl protocols.
.. code-block:: xml
You can also use the command line option ``-L `` to change the
session lifetime in the cache (10mn by default); value must be in seconds.
You can also change the way Tsung starts remote beams. By default,
Tsung will start at most 20 ssh process per core of the controller. If
you manage hundreds of clients, you may want to raise this value with
``max_ssh_startup_per_core`` (or decrease it if you wish)
.. code-block:: xml
.. index:: idle_timeout
.. index:: global_ack_timeout
Timeout for TCP connections
---------------------------------------
.. versionadded:: 1.6.0
You can specify a timeout in milliseconds for establishing a TCP connection. The default is ``infinity``.
.. code-block:: xml
You can also change the timeout on a per-session basis using ``set_option``.
.. code-block:: xml
You can also enable the TCP REUSEADDR option globally:
.. code-block:: xml
IP transparent
---------------------------------------
.. versionadded:: 1.7.0
This option is used to set the IP_TRANSPARENT option on the TCP socket
.. code-block:: xml
This can be useful to use when IPs are not configured on the client host (see also :ref:`iprange-label`)
Retry Attempts and Timeouts
---------------------------------------
.. versionadded:: 1.6.0
You can specify the amount of retry attempts made by Tsung. The default is ``3``.
.. code-block:: xml
To disable retries entirely, set the value to ``0``.
In addition, the option ``retry_timeout`` (in milliseconds; defaults to ``10``) is used to implement a
simple back-off algorithm (``retry * retry_timeout``).
.. code-block:: xml
Timeout for acknowledgments of messages
---------------------------------------
This is used to set the idle timeout(used for 'parse' and 'local' ack) and
global ack timeout(used for 'global' ack). By default, idle timeout will be
10min(600000) and global ack timeout will be ``infinity``. This value
can be changed like this:
.. code-block:: xml
.. index:: hibernate
Hibernate
---------
.. versionadded:: 1.3.1
The option ``hibernate`` is used to reduced memory consumption of
simulated users during thinktimes. By default, hibernation will be
activated for thinktimes higher than 10sec. This value can be changed
like this:
.. code-block:: xml
To disable hibernation, you must set the value to ``infinity``.
.. index:: rate_limit
Rate_limit
----------
.. versionadded:: 1.4.0
``rate_limit``. This will limit the bandwidth of each client
(using a token bucket algorithm). The value is in KBytes per
second. You can also specify a maximum burst value
(eg. ``max='2048'``). By default the burst size is the same as
the rate (1024KB in the following example). Currently, only incoming
traffic is rate limited.
.. code-block:: xml
Ports_range
-----------
If you need to open more than 30000 simultaneous connections on a
client machine, you will be limited by the number of TCP client ports,
even if you use several IPs (this is true at least on Linux). To
bypass this limit, Tsung must not delegate the selection of client
ports and together with using several IP for each client,
you have to defined a range for available clients ports, for ex:
.. code-block:: xml
.. index:: seed
Setting the seed for random numbers
------------------------------------
If you want to use a fixed seed for the random generator, you can use
the ``seed`` option, like this (by default, Tsung will use the
current time to set the seed, therefore random numbers should be
different for every test).
.. code-block:: xml
Path for BOSH
------------------
You can use the following config option for setting the path to BOSH
request:
.. code-block:: xml
.. _jabber-options-label:
Websocket options
------------------
When you use Websocket as a server type, you can set the following options
for Websocket:
.. code-block:: xml
Use ``websocket_path`` for setting the path of the websocket request; use
``websocket_frame`` for setting the frame type(option type: binary and text,
and binary as default) of the sending websocket data. Use ``websocket_subprotocols`` for setting the ``Sec-WebSocket-Protocol`` header.
XMPP/Jabber options
-------------------
Default values for specific protocols can be defined. Here is an
example of option values for Jabber/XMPP:
.. code-block:: xml
Using these values, users will be ``myuserXXX`` where *XXX* is an integer in
the interval *[1:userid_max]* and passwd ``mypasswdXXX``
If not set in the configuration file, the values will be set to:
* global_number = 100
* userid_max = 10000
* domain = erlang-projects.org
* username = tsunguser
* passwd = sesame
Other options are available if you prefer to use a CSV file for
username/password, see :ref:`sec-read-user-jabber-csv-label`.
You can also set the ``muc_service`` here (see previous example).
HTTP options
------------
For HTTP, you can set the ``UserAgent`` values
(**available since Tsung 1.1.0**), using a probability for each
value (the sum of all probabilities must be equal to 100)
.. code-block:: xml
AMQP options
------------
You can set the AMQP heartbeat timeout; for example to set it to 30s
(default is 600s), add:
.. code-block:: xml