Skip to main content

Installing and Initial setup of Tsung Load Testing CentOS

Installing and Initial setup of Tsung Load Testing CentOS

Installation on Centos

 [ahmed@server ~]$ yum install erlang 
 [ahmed@server ~]$ tar -xvzf tsung-1.5.1.tar.gz -C /opt
 [ahmed@server ~]$ cd /opt/tsung-1.5.1
 [ahmed@server ~]$ ./configure
 [ahmed@server ~]$ make
 [ahmed@server ~]$ make install
Some Version information.
 [ahmed@server ~]$ tsung -v
 Tsung version 1.5.1
 [ahmed@server ~]$ tsung
 Usage: tsung  start|stop|debug|status
 Options:
     -f      set configuration file (default is ~/.tsung/tsung.xml)
                    (use - for standard input)
     -l    set log directory where YYYYMMDD-HHMM dirs are created (default is ~/.tsung/log/)
     -i        set controller id (default is empty)
     -r   set remote connector (default is ssh)
     -s            enable erlang smp on client nodes
     -p       set maximum erlang processes per vm (default is 250000)
     -m      write monitoring output on this file (default is tsung.log)
                    (use - for standard output)
     -F            use long names (FQDN) for erlang nodes
     -w            warmup delay (default is 1 sec)
     -v            print version information and exit
     -6            use IPv6 for Tsung internal communications
     -x      list of requests tag to be excluded from the run (separated by comma)
     -h            display this help and exit
 [ahmed@server ~]$
Sample Test load.xml update load_test_machine and web_server_to_test as per the servers. 
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd" []>
 <tsung loglevel="warning">

   <clients>
  <client host="load_test_machine" cpu="2" maxusers="30000000"/>
   </clients>

   <servers>
  <server host="web_server_to_test" port="80" type="tcp"/>
   </servers>

   <load>
  <arrivalphase phase="1" duration="1" unit="minute">
    <users arrivalrate="5" unit="second"/>
  </arrivalphase>
   </load>

   <sessions>
  <session name="es_load" weight="1" type="ts_http">
    <request>
    <http url="/postdata/Information"
      method="POST"
      contents_from_file="test.json" />
    </request>
  </session>
   </sessions>
 </tsung>
Test Sample Json
 {
     "name":"ahmed",
     "age":30
 }

Next Execute the command to start the service .

 tsung -f load.xml start 
This will start the service which will start hitting the server.
All logs will be available in ${HOME}/.tsung/log
More information
 https://engineering.helpshift.com/2014/tsung/

Comments

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa