[Tsung] Configuration Problem

[Nicolas Niclausse]

Matthias Stiller ecrivait le 24.04.2008 16:57:
> Thank you.
> 
> Just to guarantee that I understood everything right please consider the 
> following (senseless) szenario. I am using Tsung 1.2.1 ...

> As far as I can see just the the connection establishment, the 
> authentication and the roster:get operations are producing response times.
> The message and presence stanzas are just to produce a specific load, 
> right? After the test I will probably get a graph ("Requests and 
> connection establishment") with a (well, very small) peak at the very 
> beginning and a sloping curve to response times of 0 mseconds. 0 
> msecdonds because the presence and message stanzas at the end are not 
> considered as being requests, right? So the green requests curve in the 
> "Requests and connection establishment"-graph just contains packets with 
> ack-type local? 

This is true with tsung 1.2.2, not with 1.2.1.

> So, collecting response times during the whole tests is 
> just possible when I have some operations in my test szenario where I 
> get a response from the server (synchronously). For example roster:add. 
> So having a roster:add or something like this in the session might be 
> very useful for analysing the response time in general ... ?!

Yes, (i don't know of roster:add is the best way to achieve this,)



With the new bidirectional stuff added in 1.2.2, we could build more 
complex scenarios:

Currently, only the response to subscribe request is implemented, but we 
could also add something to handle incoming chat messages. Then we could do 
something like this:

user1 sends a message to user2 (with ack=local)
user2 detects a msg from user1 and respond to it,
therefore user1 gets a response for its message.

-- 
Nicolas