tsung(1) [debian man page]

TSUNG(1)																  TSUNG(1)

NAME

       tsung - A distributed multi-protocol load testing tool.

SYNOPSIS

       tsung [ -f configuration file ]	[ -l log dir ]	[ -m filename ]  [ -r command ]  [ -v ]  [ -6 ]  [ -h ]  [ start|stop|debug|status ]

DESCRIPTION

       tsung  is a distributed load testing tool. It is protocol-independent and can currently be used to stress and benchmark HTTP, WebDAV, LDAP,
       PostgreSQL, MySQL and Jabber/XMPP servers.

       It simulates user behaviour using an XML description file, reports many measurements in real time (statistics can be customized with trans-
       actions, and graphics generated using gnuplot).

       For  HTTP,  it supports 1.0 and 1.1, has a proxy mode to record sessions, supports GET and POST methods, Cookies, and Basic WWW-authentica-
       tion. It also has support for SSL.

       Several config examples can be found in /usr/share/doc/tsung/examples/.

       start  start tsung load testing

       debug  start tsung with an interactive erlang shell

       stop   stop tsung

       status print current status of a running instance of tsung (must be run on the controller host)

MANUAL

       A manual should be available at /usr/share/doc/tsung/user_manual.html. It is also available online at

	      http://tsung.erlang-projects.org/user_manual.html

OPTIONS

       -f filename
	      specifies the configuration file to use. The default file name is ~/.tsung/tsung.xml. Use - for standard input

       -l logdir
	      Specifies the log directory to use. The default log dir name is ~/.tsung/log/YYYYMMDD-HHMM/

       -m monitoring_file
	      Specifies the monitoring log file name to use. The default log file name is tsung.log. Use - for standard output

       -r command
	      Specifies an alternative to ssh (rsh for ex.) for starting a slave node on a remote host

       -i id  set controller id (default is empty). Needed to start several controllers on the same host.

       -F     Use long names for erlang nodes (FQDN)

       -m     Enable erlang smp on client nodes

       -v     Show version

       -6     Use IPv6 for tsung internal communications

       -h     Show usage

BUGS

       Please reports bugs to the mailing list <tsung-users@process-one.net>, see

	      https://lists.process-one.net/mailman/listinfo/tsung-users

       for archives.

SEE ALSO

       erlang(3)

AUTHORS

       Tsung is written by Nicolas Niclausse <nicolas@niclux.org>. Contributors list is available in /usr/share/doc/tsung/CONTRIBUTORS

								   January 2004 							  TSUNG(1)

pool(3erl)						     Erlang Module Definition							pool(3erl)

NAME

       pool - Load Distribution Facility

DESCRIPTION

       pool  can  be used to run a set of Erlang nodes as a pool of computational processors. It is organized as a master and a set of slave nodes
       and includes the following features:

	 * The slave nodes send regular reports to the master about their current load.

	 * Queries can be sent to the master to determine which node will have the least load.

       The BIF statistics(run_queue) is used for estimating future loads. It returns the length of the queue of ready  to  run	processes  in  the
       Erlang runtime system.

       The slave nodes are started with the slave module. This effects, tty IO, file IO, and code loading.

       If the master node fails, the entire pool will exit.

EXPORTS

       start(Name) ->
       start(Name, Args) -> Nodes

	      Types  Name = atom()
		     Args = string()
		     Nodes = [node()]

	      Starts  a  new pool. The file .hosts.erlang is read to find host names where the pool nodes can be started. See section Files below.
	      The start-up procedure fails if the file is not found.

	      The slave nodes are started with slave:start/2,3 , passing along Name and, if provided, Args . Name is used as the first part of the
	      node names, Args is used to specify command line arguments. See slave(3erl) .

	      Access rights must be set so that all nodes in the pool have the authority to access each other.

	      The function is synchronous and all the nodes, as well as all the system servers, are running when it returns a value.

       attach(Node) -> already_attached | attached

	      Types  Node = node()

	      This function ensures that a pool master is running and includes Node in the pool master's pool of nodes.

       stop() -> stopped

	      Stops the pool and kills all the slave nodes.

       get_nodes() -> Nodes

	      Types  Nodes = [node()]

	      Returns a list of the current member nodes of the pool.

       pspawn(Mod, Fun, Args) -> pid()

	      Types  Mod = Fun = atom()
		     Args = [term()]

	      Spawns a process on the pool node which is expected to have the lowest future load.

       pspawn_link(Mod, Fun, Args) -> pid()

	      Types  Mod = Fun = atom()
		     Args = [term()]

	      Spawn links a process on the pool node which is expected to have the lowest future load.

       get_node() -> node()

	      Returns the node with the expected lowest future load.

FILES

       .hosts.erlang is used to pick hosts where nodes can be started. See net_adm(3erl) for information about format and location of this file.

       $HOME/.erlang.slave.out.HOST  is  used  for  all additional IO that may come from the slave nodes on standard IO. If the start-up procedure
       does not work, this file may indicate the reason.

Ericsson AB							   stdlib 1.17.3							pool(3erl)