Tsung Intro presentation 2013

TSUNG LOAD TESTINGTesting HTTP(S)/ Databases / LDAP/ XMPP..

<insert your plugin here>

Steffen Larsen (slarsen@braintrust)twitter: @zooldk

Uncertainty is a recipe for failure!

January 2013

Saturday, January 26, 13

TSUNG INTRO

Introduction to Tsung

Walk through the phases of a TSUNG load test

Mainly talk about using TSUNG on the HTTP protocol

Show simple use cases (my installation is fcked - sorry!)

Drink a beer!


TSUNG INTROOpen Source (GPLv2)

Based on Erlang which implicitly defines it as:

Highly concurrent and blazingly fast..

Small memory fingerprint (512 bytes for an erlang process vs. 512k default for a JVM stack for a thread)

Distributed by the nature of Erlang and easily done (so we can do DDOS!) :-)

Multi protocol: HTTP (REST, SOAP,WebDav etc), PostgreSQL, MySQL, LDAP, XMPP/Jabber. Support for SSL and Cookie handling

Easy Setup! - no confusing GUI (vi and a DTD is enough). Xorg might not be available on the servers.

The purpose of Tsung is to simulate users in order to test the scalability and performance of IP based client/server applications.


TSUNG IN HTTP LAND

Supports both old HTTP 1.0 and 1.1 (Web Sockets on a branch)

GET, POST, PUT, DELETE etc. Methods support

Cookies are automatically handled

WWW basic authentication

Basic support for SOAP using HTTP mode

Proxy mode to record sessions using a web browser..


TSUNG LIFE CYCLE

serverTsungXML

reports

0.write your tsung.xml 1.run2.tsung gen. data

3.tsung measures

4.report generation


TSUNG PHASES.. Define load clients (localhost or multiple for massive/distributed testing)

Define servers you want to load test

Define the load scenario (num. users, arrivals etc, timing)

Define your monitors (servers you are load testing AND related systems)

Record or define your user scenarios (proxy and record or manually edit config)

Run! (tsung -f config.xml start)

Grab a beer.. (cheers!)

Generate Graphs (for the data reported by tsung demon)


DEMO

show: simple_example.xml config

run: tsung -f simple_example.xml start

see the log file (default $HOME/.tsung/log/<timestamp>


RECORDING..

You can either define you data by hand in the configuration file or record it via. a proxy and a web browser.

tsung-recorder -L 9000 start (recorder will listen on port 9000)

Now start you browser, configure a new proxy and hit the page you want to record.

Use the out put in your tsung xml file and voila!


WHY TSUNG?Your own scripts with curl, wget.. - Stop that!

AB Apache Bench (slow as he..)

HTTPPerf (better but still not fast and not distributed)

JMeter (Java based) - quite good, Nice GUI, distributed! but JVM mem and consumption !

Grinder (Java based)??

Gatling-Tools (JVM, scala, looks promising..using the akka actor principle for concurrency - instead of normal threads - similar to erlang)


BURNING SERVERS 0/1?

0 1VS

load testing or load generation!


MONITOR YOUR LOAD!

Default SNMP OIDS for CPU usage, network traffic, load, memory etc. - No need to install a special agent on the tested server

Define your own OIDs! (patch in 1.4.x done by my poor erlang skills)

With this you can measure your JVM, disk, IO etc.

Network always the problem... there should be open for SNMP and the ports your are testing!


GRAPHS!

Tsung have now generated data in the log directory (default $HOME/.tsung/log.. Can be set different with -d option)

/usr/local/Cellar/tsung/1.4.2/lib/tsung/bin/tsung_stats.pl <log>

Now HTML is ready and can be served and showed off


DEMO

tsung -f monitor_example.xml start

see the log file (default $HOME/.tsung/log/<timestamp>

Generate graphs from your monitors:

/usr/local/Cellar/tsung/1.4.2/lib/tsung/bin/tsung_stats.pl <log>


TSUNG XML CONFIGMany options: set browser agents, probability for hit

Get content from files (CVS or.. define your pattern)

Mix files or code into config with substitution

Use xpath or jsonpath to MATCH on the response and make you action!

Use regular expressions as well.. (GNU RegExp)

Programmatically (use conditionals: for loops, if, repeats or variables etc. for testing)

more advanced stuff


DISTRIBUTED TESTS

Tsung distributed load testing is based on SSH shell and erlang distribution system.

Distribution is easy! just add more clients!

Remember to make network accessible for the controller and workers - ssh login with a key from controller to all the slave nodes (workers) should be available

Same version of tsung/erlang on EVERY machine (controller/workers)


DISTRIBUTED TESTS

server

TsungcontrollerXML

reports

0.write your tsung.xml 1.run

4.report generation

Tsungworker

Tsungworker

Tsungworker

generate/gather

multiple servers as workers


MORE ADVANCED STUFF

Overlay/merge your graphs, useful for comparing (tsplot)

Besides SNMP we can monitor with Munin or Erlang agents on the remote servers..

Choose another backend: text, json, rrdtool etc. (if you want another graphing tool or what ever)

Measure in realtime or generate afterwards.


MORE ADVANCED STUFF

The recording proxy also works for database protocols (query proxy)

Mix your sessions types (mysq with HTTP or XMPP ...)


TSUNG GOTCHA’S If you are new at Erlang, dumps of stack traces can be hard if anything is wrong!

Remember to write the config in the correct order of the DTD (its picky!)

The path to the DTD was wrong.. comes with funny exceptions!

Turn off debugging when testing - it takes time to write.

Ensure that your versions is the same and compiled (if not a package) in the same way if you are running distributed!


TSUNG GOTCHA’S set sysctl.conf for many client connections..

set the hard limit of “max files open” larger than 1024.

Do that on every controller and node! (otherwise you limit yourself!)

Do some tuning of the network stack! memory for TCP , read, write and backlog. Example:

net.core.rmem_max = 16777216net.core.wmem_max = 16777216net.ipv4.tcp_rmem = 4096 87380 16777216net.ipv4.tcp_wmem = 4096 65536 16777216

# This gives the kernel more memory for TCP# which you need with many (100k+) open socket connectionsnet.ipv4.tcp_mem = 50576 64768 98152

# Backlognet.core.netdev_max_backlog = 2048net.core.somaxconn = 1024net.ipv4.tcp_max_syn_backlog = 2048net.ipv4.tcp_syncookies = 1

For massive testing


TESTING PLAN GOTCHAS

Understand what you are testing

Prepare your self: write down your expectations, what went wrong and what to improve.. Use a wiki (JIRA)

Store your test for later comparison (use tsplot etc.)

Test on the correct network. Plan which one. Take into consideration that you have to reach the servers being tested (both test port and SNMP)

Prepare your network a massive load!. Be prepared that a switch will blow up or so..


LINKS ETC.http://tsung.erlang-projects.org

http://dak1n1.com/blog/14-http-load-generate

http://programmingobsession.blogspot.dk/2012/09/tsung-vs-jmeterj.html

Installation:

Mac (homebrew): brew install tsung

Linux: apt-get install tsung

Windows?

Compile your own -- a lot of dependencies..


http://tsung.erlang-projects.org

http://tsung.erlang-projects.org



Date post:	08-May-2015
Category:	Technology
Upload:	steffen-larsen
View:	4,293 times
Download:	2 times

Tsung Intro presentation 2013

Technology