If you are looking to stress test your server-side, one approach we have used is to use a tool like openSTA. It operates as a proxy, and records the interactions between your browser and the server, and records them to a script. We would record a number of scripts that model typical user interactions with our application, and then use these to load up the server with concurrent activity from different size (emulated) active user populations.
openSTA has a lot of flexibility, and the expressiveness of the scripting engine, as well as the runtime environment, allow you to model things such as variations in timings, selection of request data from a data set, support for cookies etc. The main place where you would have to do some work is in the manipulation of the POST data body - it will capture the GWT RPC serialized form of the message (assuming that you are using GWT RPC), so if you want to change parameter values, you will have to dig into the payload, and substitute the appropriate values. Here's a link - http://www.opensta.org/ Other tools for server load-testing you can look at include JMeter (http://jakarta.apache.org/jmeter/) and Grinder (http:// grinder.sourceforge.net/). Finally - don't forget that if you're doing large scale user testing, make sure the rest of your infrastructure is up to handling the test load - i.e. network connectivity, machines available to act as client machines etc. Good luck, Jason On May 28, 1:01 am, asianCoolz <[email protected]> wrote: > how do you folks stress test gwt application simulate thousands of > users using the app? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
