tsung-1.5.1/ 0000755 0001750 0001750 00000000000 12321173206 013745 5 ustar nniclausse nniclausse tsung-1.5.1/examples/ 0000755 0001750 0001750 00000000000 12321173206 015563 5 ustar nniclausse nniclausse tsung-1.5.1/examples/jabber_roster.xml.in 0000644 0001750 0001750 00000005303 12104023217 021531 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/jabber_node.xml.in 0000644 0001750 0001750 00000006654 12104023217 021152 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/mqtt.xml.in 0000644 0001750 0001750 00000003614 12236145741 017713 0 ustar nniclausse nniclausse
test_message
tsung-1.5.1/examples/jabber.xml.in 0000644 0001750 0001750 00000010172 12104023217 020133 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/jabber_muc.xml.in 0000644 0001750 0001750 00000006075 12104023217 021006 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/mysql.xml.in 0000644 0001750 0001750 00000002165 12104023217 020056 0 ustar nniclausse nniclausse
SHOW TABLES
SELECT * FROM gens
SELECT * FROM te
tsung-1.5.1/examples/ldap.xml.in 0000644 0001750 0001750 00000004703 12104023217 017631 0 ustar nniclausse nniclausse
organizationalPerson
inetOrgPerson
person
%%_new_user_cn%%
fffs
SomeSN
some@mail.com
tsung-1.5.1/examples/http-digest.xml.in 0000644 0001750 0001750 00000004142 12104023217 021142 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/websocket.xml.in 0000644 0001750 0001750 00000002372 12236145741 020714 0 ustar nniclausse nniclausse
{"user":"user", "password":"password"}
ok
{"uid":"%%_uid%%", "data":"data"}
{"key":"value"}
tsung-1.5.1/examples/pgsql.xml.in 0000644 0001750 0001750 00000003442 12104023217 020036 0 ustar nniclausse nniclausse
SELECT * from accounts;
SELECT * from users;
tsung-1.5.1/examples/amqp.xml.in 0000644 0001750 0001750 00000010756 12236145741 017671 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/fs-nfs.xml.in 0000644 0001750 0001750 00000007363 12104023217 020112 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/http_setdynvars.xml.in 0000644 0001750 0001750 00000005646 12212102345 022161 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/jabber_register.xml.in 0000644 0001750 0001750 00000002455 12104023217 022044 0 ustar nniclausse nniclausse
error
tsung-1.5.1/examples/http_distributed.xml.in 0000644 0001750 0001750 00000014360 12104023217 022272 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/thinks2.xml.in 0000644 0001750 0001750 00000002264 12104023217 020273 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/jabber_privacy.xml.in 0000644 0001750 0001750 00000003176 12212102345 021676 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/http-oauth.xml.in 0000644 0001750 0001750 00000004723 12104023217 021010 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/http_simple.xml.in 0000644 0001750 0001750 00000004240 12104023217 021235 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/http_tag.xml.in 0000644 0001750 0001750 00000002411 12236145741 020532 0 ustar nniclausse nniclausse
tsung-1.5.1/examples/thinks.xml.in 0000644 0001750 0001750 00000002276 12104023217 020214 0 ustar nniclausse nniclausse
tsung-1.5.1/man/ 0000755 0001750 0001750 00000000000 12321173206 014520 5 ustar nniclausse nniclausse tsung-1.5.1/man/tsplot.1 0000644 0001750 0001750 00000013750 12236145741 016145 0 ustar nniclausse nniclausse .\" auto-generated by docbook2man-spec from docbook-utils package
.TH "TSPLOT" "1" "February 2007" "" ""
.SH NAME
tsplot \- Plot several tsung logs on the same charts, for comparison purpose.
.SH SYNOPSIS
.sp
\fBtsplot\fR [ \fB-c configuration file\fR ] [ \fB-d images output directory\fR ] [ \fB-v verbose\fR ] [ \fBlegend logfile\fR ]
.SH "DESCRIPTION"
.PP
Tsung comes with a plotting tool using
\fBgnuplot\fR, producing some graphs from the
\fItsung.log\fR file data.
\fBtsplot\fR is able to plot data from several
\fItsung.log\fR files onto the same charts serie,
for further comparison and analyze.
.SH "OPTIONS"
.PP
.TP
\fB-c\fR
.TP
\fB--config\fR
specifies the configuration file to use. Default is \fIhttp.en.plots.conf\fR\&.
.TP
\fB-d\fR
.TP
\fB--outdir\fR
directory where \fBtsplot\fR saves the images
it produces, defaults to \fI/tmp/tsung\fR\&.
.TP
\fB-v\fR
.TP
\fB--verbose\fR
makes \fBtsplot\fR very verbose about
what it does.
.SH "CONFIGURATION"
.PP
The configuration file of \fBtsplot\fR allows one to
define the plots you want to obtain, from their label to the
data they will show. The configuration file adopts a
\fI\&.ini\fR file syntax, each section defining a
chart.
.PP
\fBtsplot\fR comes with two sample configuration
files, namely \fIhttp.plots.en.conf\fR and
\fIpgsql.plots.en.conf\fR\&. They respectively define
charts to be plotted for a \fBtsung\fR HTTP test
and a \fBtsung\fR PGSQL test.
.PP
A \fBDEFAULT\fR section may be provided, any
element configured here may then be overridden into a specific
plot section.
.PP
Another configuration file is used by \fBtsplot\fR:
the \fItsung/stats.conf\fR one. It's used to
define by type the statistics to be read into
\fBtsung\fR log files, and you shouldn't need to
edit it, short of adding support for new
\fBtsung\fR statistics.
.PP
Common settings, to be found into \fBDEFAULT\fR
section or any specific chart section.
.TP
\fBencoding\fR
set here the encoding used thereafter in the file, for
labels and titles.
.TP
\fBdpi\fR
dpi setting of produced charts images
.TP
\fBtn_dpi\fR
dpi setting of produced charts thumbnail images
.TP
\fBimgtype\fR
type of chart image to produce, as in
\fIpng\fR or \fIps\fR
A complete list might be obtained on the
\fBpython-matplotlib\fR website,
http://matplotlib.sourceforge.net/
.TP
\fBxlabel\fR
default label for horizontal axe, often you want seconds
or minutes, depending on xfactor.
Please note you can also set some defaults for ylabel, but
this seems not to be a good idea in practise.
.TP
\fBxfactor\fR
tsung logs statistics in its logfile every 10 seconds. By
default, charts will not scale this and have seconds as
horizontal axis units. By setting an xfactor of 60, you
have a minute precision on horizontal axis.
.TP
\fByfactor\fR
same as xfactor, but for vertical axis.
Depending on the data you obtain with your tests, you may
want to adapt the vertical scale of your plotting. For
example, the \fBpage.mean\fR statistic is
logged in milliseconds by \fBtsung\fR\&. You
may want to display seconds if this unit better fits your
measures. Then simply set \fByfactor =
1000\fR\&.
.TP
\fBstyles\fR
set here any number of \fBmatplotlib\fR
styles you want to use, separated by spaces, as available
here:
http://matplotlib.sourceforge.net/matplotlib.pylab.html#-plot.
For exemple, set \fBstyles = b- g+ r- cx\fR
for plotting first dataset (see \fBstats\fR
below) with a blue solid line, second with green plus
symbols, third with a red line and last with cyan cross
symbols.
This could fit a \fBstats = 200.count
400.count\fR stats setting when plotting two
\fBtsung\fR logs.
.PP
You then can define any number of plot, one by section, and give
them an arbitrary name. The name must be unique, and will be
used for naming output images.
.PP
.PP
Any option available in DEFAULT section is also available in any
specific chart section, with the same meaning and effect. The
specific setting will systematically override the DEFAULT one.
.PP
.TP
\fBtitle\fR
Title of the chart, as printed into the resulting image.
.TP
\fBstats\fR
The statistics properties to use for this plotting, as
named in the \fItsung/stats\fR
configuration file. Please see this bundled file for a
list of what is available.
Tsung provide several types of statistics, as documented
here:
http://tsung.erlang-projects.org/user_manual.html#htoc53. The
two main types of statistics used are
\fBsample\fR and \fBcounter\fR\&. A
third one is \fBgauge\fR but is only use for a
single statistic (users).
sample provides count, mean, stdvar, max, min and gmean
(global mean)
properties, and counter provides only count and
totalcount. gauge provide count and max.
The stats setting can accept several
\fBstat.property\fR elements, separated by
spaces.
Examples: \fBstats = users.count\fR to plot
the number of simultaneously connected users, and
\fBstats = 200.count 400.count\fR to plot
given HTTP return codes count, both on the same chart.
Please notice \fBtsplot\fR is currently
limited to use only one horizontal and only one vertical
scales. \fBmatplotlib\fR is able to define
some more complex drawings, but \fBtsplot\fR
is not yet able to benefit from this.
.TP
\fBlegend\fR
Legend prefix, which will be followed by the legend given
on command line.
Each plot on a chart has a legend entry, you configure
here the meaning of the plot (say 'concurrent users') and
\fBtsplot\fR will add it the name of the data
serie being plotted (say 'scenario x'). You'd obtain this
legend: 'concurrent users scenario x'.
.TP
\fBylabel\fR
label for vertical axe
.SH "CONFIGURATION EXAMPLE"
.PP
Please see the given configuration examples which should be
distributed in
\fI/usr/share/doc/tsung/tsung-plotter/http.plots.en.conf\fR
and
\fI/usr/share/doc/tsung/tsung-plotter/pgsql.plots.en.conf\fR\&.
.SH "BUGS"
.PP
Please reports bugs to the mailing list
or in the bug
tracker ,
see also for
archives.
.SH "AUTHORS"
.PP
\fBtsplot\fR is written by Dimitri Fontaine
\&.
tsung-1.5.1/man/tsung.1 0000644 0001750 0001750 00000005234 12236145741 015756 0 ustar nniclausse nniclausse .\" auto-generated by docbook2man-spec from docbook-utils package
.TH "TSUNG" "1" "January 2004" "" ""
.SH NAME
tsung \- A distributed multi-protocol load testing tool.
.SH SYNOPSIS
.sp
\fBtsung\fR [ \fB-f configuration file\fR ] [ \fB-l log dir\fR ] [ \fB-m filename\fR ] [ \fB-r command\fR ] [ \fB-v\fR ] [ \fB-6\fR ] [ \fB-h\fR ] [ \fBstart|stop|debug|status\fR ]
.SH "DESCRIPTION"
.PP
\fBtsung\fR 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.
.PP
It simulates user behaviour using an XML description file,
reports many measurements in real time (statistics can be
customized with transactions, and graphics generated using
gnuplot).
.PP
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-authentication. It also has support for SSL.
.PP
Several config examples can be found in
\fI/usr/share/doc/tsung/examples/\fR\&.
.TP
\fBstart\fR
start tsung load testing
.TP
\fBdebug\fR
start tsung with an interactive erlang shell
.TP
\fBstop\fR
stop tsung
.TP
\fBstatus\fR
print current status of a running instance of tsung (must be run on the controller host)
.SH "MANUAL"
.PP
A manual should be available at
\fI/usr/share/doc/tsung/user_manual.html\fR\&. It
is also available online at
.sp
.RS
.sp
.nf
http://tsung.erlang-projects.org/user_manual.html
.sp
.fi
.RE
.sp
.SH "OPTIONS"
.TP
\fB-f filename\fR
specifies the configuration file to use. The default
file name is \fI~/.tsung/tsung.xml\fR\&. Use - for standard input
.TP
\fB-l logdir\fR
Specifies the log directory to use. The default log dir name is \fI~/.tsung/log/YYYYMMDD-HHMM/\fR
.TP
\fB-m monitoring_file\fR
Specifies the monitoring log file name to use. The
default log file name
is \fItsung.log\fR\&. Use - for standard output
.TP
\fB-r command\fR
Specifies an alternative to ssh (rsh for ex.) for starting a slave node on a remote host
.TP
\fB-i id\fR
set controller id (default is empty). Needed to start
several controllers on the same host.
.TP
\fB-F\fR
Use long names for erlang nodes (FQDN)
.TP
\fB-m\fR
Enable erlang smp on client nodes
.TP
\fB-v\fR
Show version
.TP
\fB-6\fR
Use IPv6 for tsung internal communications
.TP
\fB-h\fR
Show usage
.SH "BUGS"
.PP
Please reports bugs to the mailing list
, see
.sp
.RS
.sp
.nf
https://lists.process-one.net/mailman/listinfo/tsung-users
.sp
.fi
.RE
.sp
for
archives.
.SH "SEE ALSO"
.PP
\fBerlang\fR(3)
.SH "AUTHORS"
.PP
\fBTsung\fR is written by Nicolas Niclausse
\&. Contributors list
is available in
\fI/usr/share/doc/tsung/CONTRIBUTORS\fR
tsung-1.5.1/man/tsung-recorder.1.sgml 0000644 0001750 0001750 00000012406 12236145741 020521 0 ustar nniclausse nniclausse
nicolas.niclausse@niclux.org
Nicolas
Niclausse
March 2009
2009
Nicolas Niclausse
tsung-recorder
1
tsung-recorder
Proxy recorder for the tsung load testing tool.
tsung-recorder
log file
command
plugin
listen port
IP
port
start|stop|restart|record_tag
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. tsung-recorder can be
used to record sessions (only for HTTP, WebDAV and Postgresql) that can be edited and replayed later by tsung
tsung-recorder is a proxy that records a session in the
tsung native XML format; it can be used by your favorite client (browser in the case of the http plugin).
start the proxy recorder (listening port is 8090). By default the HTTP recorder is started. With the option, you can select another plugin. The resulting files will be created as ~/.tsung/tsung_recorderYYYMMDD-HH:MM.xml; if it doesn't work, take a look at ~/.tsung/log/tsung.log-tsunami_recorder@hostname
stop the proxy recorder
value
add a string (comment or tag) while recording a
session. This is useful for example to add transaction tag
while recording a session.
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
Specifies the log file to use. The default log file name is ~/tsung/log/tsung.log
Specifies the plugin used for the recorder. Default is
http, available: http, pgsql, webdav
Listening port for the recorder. Default is 8090
For the pgsql recorder (or parent proxy): server IP. default is 127.0.0.1
For the pgsql recorder (or parent proxy): server port. Default is 5432
For the http recorder: use a parent proxy
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
erlang3
and tsung1
Authors
Tsung is written by Nicolas Niclausse
nicolas@niclux.org. Contributors list
is available in
/usr/share/doc/tsung/CONTRIBUTORS
tsung-1.5.1/man/Design_fr.txt 0000644 0001750 0001750 00000006022 12236145741 017171 0 ustar nniclausse nniclausse
Arbre de supervision OTP:
========================
tsung est divisé en deux applications aux sens OTP:
** un controlleur unique (tsung_controller)
* ts_config_server (gen_server). Serveur de configuration server. La
définition des sessions est gardé part le serveur de configuration.
* ts_mon (gen_server)
* ts_os_mon (gen_server)
* ts_timer (utilisé par ts_client en global) (gen_fsm)
serveurs utilisés pour construire les messages:
* ts_msg_server (gen_server)
* ts_user_server (gen_server) utilisé par ts_launcher et jabber_*
pour l'unicité des utilisateurs
** plusieurs injecteurs (tsung). Plusieus noeuds peuvent être actifs
simultanément
* ts_launcher (gen_fsm) lance les clients simulés (selon un processus de
Poisson).
* ts_session_cache (gen_server) cache les sessions (interroge le
config_server si la session n'est pas encore dans le cache)
* 1 processus erlang par client simulé (ts_client), sous la
supervision de ts_client_sup (simple_one_for_one)
Le principaux modules sont:
==========================
1/ ts_launcher. Le processus maître qui va lancer les autres
processus (un par beam)
1.1/ processus clients initiant les connexions TCP
(module ts_client). Ces processus sont lancés par le processus
maître avec un intervalle de temps suivant une distribution de
probabilité exponentielle d'intensité paramétrable au démarrage
(unité = sec). Le nombre de clients total est également
paramétrable au démarrage du processus maître (il s'agit bien du
nombre de client total et non du nombre de clients simultanés)
1.2/ Le processus de monitoring (module ts_mon)
2/ Un module pour gérer les échantillons aléatoires (module ts_stats)
4/ Les modules spécifiques pour gérer les différents protocoles (module
ts_jabber ou ts_http par ex.).
Comment rajouter un nouveau protocole ou étendre un existant:
============================================================
Tout protocole doit exporter les fonctions suivantes:
-export([init_dynparams/0,
add_dynparams/4,
get_message/1,
session_defaults/0,
parse/2,
parse_config/2,
new_session/0]).
cf. fichier template doc/ts_template.erl
Références:
==========
- Erlang
http://www.erlang.org/
Design principles:
http://www.erlang.org/doc/r7b/doc/design_principles/part_frame.html
- Jabber
http://docs.jabber.org/general/html/protocol.html
- modélisation stochastiques :
Plus de détails sur ce type de modélisation sont disponibles dans les
documents suivants (dans le contexte du protocole HTTP)
Nicolas Niclausse. Modélisation, analyse de performance et
dimensionnement du World Wide Web. Thèse de Doctorat, Université
de Nice - Sophia Antipolis, Juin 1999.
http://www-sop.inria.fr/mistral/personnel/Nicolas.Niclausse/these.html
Z. Liu, N. Niclausse, C. Jalpa-Villanueva & S. Barbier. Traffic
Model and Performance Evaluation of Web Servers Rapport de
recherche INRIA, RR-3840 (http://www.inria.fr/rrrt/rr-3840.html)
tsung-1.5.1/man/tsung-recorder.1 0000644 0001750 0001750 00000005076 12236145741 017565 0 ustar nniclausse nniclausse .\" auto-generated by docbook2man-spec from docbook-utils package
.TH "TSUNG-RECORDER" "1" "March 2009" "" ""
.SH NAME
tsung-recorder \- Proxy recorder for the tsung load testing tool.
.SH SYNOPSIS
.sp
\fBtsung-recorder\fR [ \fB-l log file\fR ] [ \fB-r command\fR ] [ \fB-p plugin\fR ] [ \fB-L listen port\fR ] [ \fB-I IP\fR ] [ \fB-P port\fR ] [ \fB-u \fR ] [ \fBstart|stop|restart|record_tag\fR ]
.SH "DESCRIPTION"
.PP
\fBtsung\fR 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. \fBtsung-recorder\fR can be
used to record sessions (only for HTTP, WebDAV and Postgresql) that can be edited and replayed later by tsung
.PP
tsung-recorder is a proxy that records a session in the
tsung native XML format; it can be used by your favorite client (browser in the case of the http plugin).
.TP
\fBstart\fR
start the proxy recorder (listening port is 8090). By default the HTTP recorder is started. With the \fB-p\fR option, you can select another plugin. The resulting files will be created as \fI~/.tsung/tsung_recorderYYYMMDD-HH:MM.xml\fR; if it doesn't work, take a look at \fI~/.tsung/log/tsung.log-tsunami_recorder@hostname\fR
.TP
\fBstop\fR
stop the proxy recorder
.TP
\fBrecord_tag value\fR
add a string (comment or tag) while recording a
session. This is useful for example to add transaction tag
while recording a session.
.SH "MANUAL"
.PP
A manual should be available at
\fI/usr/share/doc/tsung/user_manual.html\fR\&. It
is also available online at
.sp
.RS
.sp
.nf
http://tsung.erlang-projects.org/user_manual.html
.sp
.fi
.RE
.sp
.SH "OPTIONS"
.TP
\fB-l logfile\fR
Specifies the log file to use. The default log file name is \fI~/tsung/log/tsung.log\fR
.TP
\fB-p plugin\fR
Specifies the plugin used for the recorder. Default is
http, available: http, pgsql, webdav
.TP
\fB-L port\fR
Listening port for the recorder. Default is 8090
.TP
\fB-I IP\fR
For the pgsql recorder (or parent proxy): server IP. default is 127.0.0.1
.TP
\fB-P port\fR
For the pgsql recorder (or parent proxy): server port. Default is 5432
.TP
\fB-u\fR
For the http recorder: use a parent proxy
.SH "BUGS"
.PP
Please reports bugs to the mailing list
, see
.sp
.RS
.sp
.nf
https://lists.process-one.net/mailman/listinfo/tsung-users
.sp
.fi
.RE
.sp
for
archives.
.SH "SEE ALSO"
.PP
\fBerlang\fR(3)
and \fBtsung\fR(1)
.SH "AUTHORS"
.PP
\fBTsung\fR is written by Nicolas Niclausse
\&. Contributors list
is available in
\fI/usr/share/doc/tsung/CONTRIBUTORS\fR
tsung-1.5.1/man/Jabber.txt 0000644 0001750 0001750 00000001372 12236145741 016461 0 ustar nniclausse nniclausse Requirements:
============
users has to be already registered:
tsung users name : cXX
passwd: pasXX
where XX is a integer between 1 and the maximum number of users (say 1000000).
or you can use jabber_register (see below).
optional parameters: (can be set in tsung.xml file)
==================
jabber_domain=mydomain.com
modules implemented for the Jabber protocol:
============================================
- jabber_common: module regrouping common functions for building
messages
NOTE: currently, no XML parsing is done by the receiving process (it
would be very time consuming to parse thousands of simultaneous XML
flows). It use acknoledgements instead based on the first packet
received after the request has been sent.
tsung-1.5.1/man/tsplot.1.sgml 0000644 0001750 0001750 00000025543 12236145741 017111 0 ustar nniclausse nniclausse
dim@tapoueh.org
Dimitri
Fontaine
February 2007
2006-2007
Dimitri Fontaine
tsplot
1
tsplot
Plot several tsung logs on the same charts, for comparison purpose.
tsplot
configuration file
images output directory
verbose
legend logfile
DESCRIPTION
Tsung comes with a plotting tool using
gnuplot, producing some graphs from the
tsung.log file data.
tsplot is able to plot data from several
tsung.log files onto the same charts serie,
for further comparison and analyze.
OPTIONS
specifies the configuration file to use. Default is http.en.plots.conf.
directory where tsplot saves the images
it produces, defaults to /tmp/tsung.
makes tsplot very verbose about
what it does.
CONFIGURATION
The configuration file of tsplot allows one to
define the plots you want to obtain, from their label to the
data they will show. The configuration file adopts a
.ini file syntax, each section defining a
chart.
tsplot comes with two sample configuration
files, namely http.plots.en.conf and
pgsql.plots.en.conf. They respectively define
charts to be plotted for a tsung HTTP test
and a tsung PGSQL test.
A DEFAULT section may be provided, any
element configured here may then be overridden into a specific
plot section.
Another configuration file is used by tsplot:
the tsung/stats.conf one. It's used to
define by type the statistics to be read into
tsung log files, and you shouldn't need to
edit it, short of adding support for new
tsung statistics.
Common settings, to be found into DEFAULT
section or any specific chart section.
set here the encoding used thereafter in the file, for
labels and titles.
dpi setting of produced charts images
dpi setting of produced charts thumbnail images
type of chart image to produce, as in
png or ps
A complete list might be obtained on the
python-matplotlib website,
http://matplotlib.sourceforge.net/
default label for horizontal axe, often you want seconds
or minutes, depending on xfactor.
Please note you can also set some defaults for ylabel, but
this seems not to be a good idea in practise.
tsung logs statistics in its logfile every 10 seconds. By
default, charts will not scale this and have seconds as
horizontal axis units. By setting an xfactor of 60, you
have a minute precision on horizontal axis.
same as xfactor, but for vertical axis.
Depending on the data you obtain with your tests, you may
want to adapt the vertical scale of your plotting. For
example, the page.mean statistic is
logged in milliseconds by tsung. You
may want to display seconds if this unit better fits your
measures. Then simply set yfactor =
1000.
set here any number of matplotlib
styles you want to use, separated by spaces, as available
here:
http://matplotlib.sourceforge.net/matplotlib.pylab.html#-plot.
For exemple, set styles = b- g+ r- cx
for plotting first dataset (see stats
below) with a blue solid line, second with green plus
symbols, third with a red line and last with cyan cross
symbols.
This could fit a stats = 200.count
400.count stats setting when plotting two
tsung logs.
You then can define any number of plot, one by section, and give
them an arbitrary name. The name must be unique, and will be
used for naming output images.
Any option available in DEFAULT section is also available in any
specific chart section, with the same meaning and effect. The
specific setting will systematically override the DEFAULT one.
Title of the chart, as printed into the resulting image.
The statistics properties to use for this plotting, as
named in the tsung/stats
configuration file. Please see this bundled file for a
list of what is available.
Tsung provide several types of statistics, as documented
here:
http://tsung.erlang-projects.org/user_manual.html#htoc53. The
two main types of statistics used are
sample and counter. A
third one is gauge but is only use for a
single statistic (users).
sample provides count, mean, stdvar, max, min and gmean
(global mean)
properties, and counter provides only count and
totalcount. gauge provide count and max.
The stats setting can accept several
stat.property elements, separated by
spaces.
Examples: stats = users.count to plot
the number of simultaneously connected users, and
stats = 200.count 400.count to plot
given HTTP return codes count, both on the same chart.
Please notice tsplot is currently
limited to use only one horizontal and only one vertical
scales. matplotlib is able to define
some more complex drawings, but tsplot
is not yet able to benefit from this.
Legend prefix, which will be followed by the legend given
on command line.
Each plot on a chart has a legend entry, you configure
here the meaning of the plot (say 'concurrent users') and
tsplot will add it the name of the data
serie being plotted (say 'scenario x'). You'd obtain this
legend: 'concurrent users scenario x'.
label for vertical axe
CONFIGURATION EXAMPLE
Please see the given configuration examples which should be
distributed in
/usr/share/doc/tsung/tsung-plotter/http.plots.en.conf
and
/usr/share/doc/tsung/tsung-plotter/pgsql.plots.en.conf.
BUGS
Please reports bugs to the mailing list
tsung-users@process-one.net or in the bug
tracker ,
see also for
archives.
AUTHORS
tsplot is written by Dimitri
Fontaine
dim@tapoueh.org.
tsung-1.5.1/man/tsung-inside.png 0000644 0001750 0001750 00000104014 12236145741 017647 0 ustar nniclausse nniclausse ‰PNG
IHDR õ ú ‘|B“ sBITÛáOà IDATxœìy\TUûÀŸÙØÅaßDA\5TÄ •E—pCSÃ~.¸¥fbîk¹”¾j&©$fjfQ`¨ ¥Eîb†J*(¢àÈ.Ìòûãâõ:wöíù~ø¼ïsÏ=çLÂwžyî¹ç0D" ‚ F[×@}!*2J×C@UIÏH'Ñï •””¤ëQ ˆªDEF‘Šgêv(¢ Ü£!))‰ü&Š~GL”;bdŠG¿#‚'˜G%)ÈIÑõõàÕm”®‡ ÐÜ]¸º¢*¼ÒÊ‚œ£T<ægDaPîÆñïh”߯Ðï¢(wcÂXÿ51?ƒ ˆîqû`¥ùEǶ4µs vIy›¡sg&
¸ À2ë7)Åì^¡ˆÍzÙóÊøñ<__x+ D–æMîÎõ}ºWM‰ÚZ‹%ÚXþ±¯UÊï6¿üa–WØÐµ/q…¶ßªA¿#ˆò45ñ—¬ßûäi©¹ÇÅÉîóeÿ7uÞ&