diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_SUBTHREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_SUBTHREADS.xml
new file mode 100644
index 00000000..6c8e3e62
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_SUBTHREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation" method="POST">
+                <http_header name="Function-Name" value="GET_POPULAR_SUBTHREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_THREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_THREADS.xml
new file mode 100644
index 00000000..66782652
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_POPULAR_THREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation" method="POST">
+                <http_header name="Function-Name" value="GET_POPULAR_THREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_SUBTHREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_SUBTHREADS.xml
new file mode 100644
index 00000000..3e369129
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_SUBTHREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="GET_RECOMMENDED_SUBTHREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_THREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_THREADS.xml
new file mode 100644
index 00000000..cf21e1dc
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_THREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="GET_RECOMMENDED_THREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_USERS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_USERS.xml
new file mode 100644
index 00000000..0915decb
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_GET_RECOMMENDED_USERS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="GET_RECOMMENDED_USERS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_SUBTHREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_SUBTHREADS.xml
new file mode 100644
index 00000000..3b045233
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_SUBTHREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation" method="POST">
+                <http_header name="Function-Name" value="UPDATE_POPULAR_SUBTHREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_THREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_THREADS.xml
new file mode 100644
index 00000000..c0a9754a
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_POPULAR_THREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation" method="POST">
+                <http_header name="Function-Name" value="UPDATE_POPULAR_THREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_SUBTHREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_SUBTHREADS.xml
new file mode 100644
index 00000000..c268f5c6
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_SUBTHREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="UPDATE_RECOMMENDED_SUBTHREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_THREADS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_THREADS.xml
new file mode 100644
index 00000000..d6df62f5
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_THREADS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="UPDATE_RECOMMENDED_THREADS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_USERS.xml b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_USERS.xml
new file mode 100644
index 00000000..de4f1111
--- /dev/null
+++ b/load testing scripts/Recommendation_App/Performance/Recommendation_App_UPDATE_RECOMMENDED_USERS.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/recommendation/?username=Manta" method="POST">
+                <http_header name="Function-Name" value="UPDATE_RECOMMENDED_USERS" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Search_App/Performance/Search_App_SEARCH_SUBTHREAD.xml b/load testing scripts/Search_App/Performance/Search_App_SEARCH_SUBTHREAD.xml
new file mode 100644
index 00000000..70dcaea6
--- /dev/null
+++ b/load testing scripts/Search_App/Performance/Search_App_SEARCH_SUBTHREAD.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/search" method="POST" contents="{&quot;searchKeywords&quot;: &quot;ice cream&quot;}" version="1.1">
+                <http_header name="Function-Name" value="SEARCH_SUBTHREAD" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>
diff --git a/load testing scripts/Search_App/Performance/Search_App_SEARCH_THREAD.xml b/load testing scripts/Search_App/Performance/Search_App_SEARCH_THREAD.xml
new file mode 100644
index 00000000..bb97c4e4
--- /dev/null
+++ b/load testing scripts/Search_App/Performance/Search_App_SEARCH_THREAD.xml	
@@ -0,0 +1,92 @@
+<?xml version="1.0"?>
+<!DOCTYPE tsung SYSTEM "/usr/share/tsung/tsung-1.0.dtd">
+<!-- set dumptraffic="true" to dump all received and sent packets -->
+<!-- set loglevel="debug" for maximum verbosity -->
+<tsung loglevel="debug" dumptraffic="true" version="1.0">
+
+    <!-- Client side setup -->
+    <clients>
+        <!-- maxusers is the max number of simultaneous clients. Don't set
+        it too high because you can run out of file descriptors,
+        ssl_esock use 2 fds by connection. -->
+
+        <client host="localhost"  maxusers="500" use_controller_vm="false"/>
+
+        <!-- Several virtual IP can be used to simulate more
+        machines. Very useful when a load-balancer use the client's IP to
+        distribute the traffic amoung a cluster of servers-->
+        <!-- <ip value="192.168.2.223"></ip> -->
+        <!-- <ip value="192.168.2.224"></ip> -->
+        <!-- </client> -->
+
+        <!-- a second machine is used, with a higher weight, and 2 cpus
+        (erlang is not SMP aware, so we starts 2 beams to use all the
+        CPUs -->
+        <!-- <client host="myhost2" weight="3" maxusers="250" cpu="2">
+        <ip value="192.168.2.225"></ip>
+        </client> -->
+
+        <!-- If you have a single machine to do the tests, you may add
+        this attribute to the client tag: use_controller_vm="true" . This
+        will run the virtual users on the same Virtual Machine as the
+        controller. Useful if you have problems with starting up remote
+        beam -->
+
+    </clients>
+
+    <!-- Server side setup -->
+    <!-- Specify where the server is to test
+    multiple servers can be defined for distributed testing -->
+    <servers>
+        <server host="localhost" port="8080" type="tcp"/>
+    </servers>
+
+    <!-- to start os monitoring (cpu, network, memory). Use an erlang
+    agent on the remote machine or SNMP. Erlang is the default
+    The web interface is running at port 8091 -->
+
+    <monitoring>
+        <monitor host="localhost" type="erlang"></monitor>
+    </monitoring>
+
+    <!-- several arrival phases can be set: for each phase, you can set
+    the mean inter-arrival time between new clients and the phase
+    duration -->
+    <load>
+        <arrivalphase phase="1" duration="100" unit="second">
+            <!--users arrivalrate="1" unit="second"></users-->
+            <users interarrival="10" unit="second"></users>
+        </arrivalphase>
+        <!-- <arrivalphase phase="2" duration="1" unit="minute"> -->
+            <!--users arrivalrate="0.1" unit="second"></users-->
+         <!--   <users interarrival="40" unit="second"></users> 
+        </arrivalphase> -->
+    </load>
+
+    <options>
+
+        <!-- HTTP parameters -->
+        <!-- If you want to benchmark a proxy server
+        instead of a reguler web server-->
+        <!--   <default type="ts_http" name="http_use_server_as_proxy" value="true"/> -->
+
+        <!-- Specify the virtual agent's browser, and the probabilty of each
+        new agent spawning each -->
+
+        <option type="ts_http" name="user_agent">
+            <user_agent probability="80">Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21</user_agent>
+            <user_agent probability="20">Mozilla/5.0 (Windows; U; Windows NT 5.2; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4</user_agent>
+        </option>
+    </options>
+
+    <sessions>
+        <session name="http-example" probability="100" type="ts_http">
+            <request>
+                <http url="/api/search" method="POST" contents="{&quot;searchKeywords&quot;: &quot;thread&quot;}" version="1.1">
+                <http_header name="Function-Name" value="SEARCH_THREAD" />
+                <http_header name="Content-Type" value="application/json" />
+                </http>
+            </request>
+        </session>
+    </sessions>
+</tsung>