Dennis Sosnoski wrote:Google WS is a great example, but difficult to use for performance testing purposes (without having a Google server in-house). I have my own sample service that looks up earthquakes from an in-memory dataset and can be queried by for range matches in latitude/longitude, date, magnitude, etc. This lets me generate sequences of pseudo-random queries that give reasonably consistent response sizes (so I can easily test how the response size effects the performance). I can generate the same sequence of queries from each test client, and easily cross-check results by adding up the total number of quakes returned for the whole sequence of queries.
I've got my own lightweight SOAP framework built around JiBX. I'll try to get something out about that, probably adding it as a subproject in conjunction with the beta 3a release next week, so that people who are interested in a decoupled approach will have something to try.
what do you use as as example service to test for doc/lit? i was thinking about Google WS but maybe there is something better?
I've been planning to implement an XMLBeans data binding to the schema for a set of data binding performance tests (separate from the web services performance tests). We're having a panel on Java data binding technologies at JavaOne, and I want to make sure people get to see some hard performance numbers, especially since JiBX blows everything else out of the water. :-) If you're interested, let's take the discussion off the list and I'll send you schema and such to look over.
- Dennis
