The dropoff at the end is because all users had joined (I had to cap the number of users based on the number of client machines). The dip in the middle of the graph seemed to correlate to the tsung node maxing out its CPUs. I’m guessing it was busy recording latency information, error rates etc.
The CPU on the phoenix server was ~40-50% during the entire benchmark. So We are probably seeing a reasonable approximation of best performance, but it seems that it almost certainly could have done more.
