Hi, everybody. Ever since rSmart shared the performance test automation work
they've been doing[1] I've been itching to try it out. It's based on a tool
call tsung[2], which is pretty similar to something like JMeter or the Grinder,
but it seems simpler to use and it's written in erlang, so it excels at
concurrency. It's my understanding that it can generate far more load from a
small client machine than other tools.
I made a couple of screencasts demonstrating it. The first one shows setting up
the browser proxy, recording some behavior, and then starting a test:
http://screencast.com/t/2jJOu3DDxtx (5 minutes)
The second one is much shorter and just shows how to generate the reports (read
pretty pictures) after a test run:
http://screencast.com/t/mp9Ux2Y5vD (1 minute, 40)
Kyle's code introduces an abstraction layer for generating the file that drives
the tsung tests. Getting familiar with tsung is an important first step to
doing that. Since we are becoming performance and scaling focused, I think it
would be good for everybody on the team to be conversant with these tools.
Comments or suggestions?
regards,
Zach
[1] https://github.com/kcampos/Open-Performance-Automation-Framework
[2] http://tsung.erlang-projects.org/
_______________________________________________
oae-dev mailing list
[email protected]
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
