Depends on what you actually want to measure. As you already point out, measuring AJAX apps is different. Here's a simple approach that I would take - I admit it's not perfect, but at least it's simple :-)
- Decide on a scenario - Execute the scenario on both - Measure total time - Measure total bandwidth (e.g. using Wireshark, which can do packet filtering, or a similar tool.) This won't give me individual time/bandwidth per request, but this is a simple first approach I would take. For me, this measurement is often more important than individual times (which are especially hard to compare, if you have multiple parallel requests in your AJAX apps). Chris On Feb 22, 3:00 pm, dhartford <[email protected]> wrote: > and please, be reasonable, saying 'use speedtracer' doesn't help -- > how do you use speedtracer to get a bandwidth/size number for a screen/ > scenario and the response time (too much detail there for simple > metric comparisons of an old site to a new site). > > On Feb 22, 8:56 am, dhartford <[email protected]> wrote: > > > > > Hi all, > > As I'm sure most of us here on the forum are doing, not everything is > > a new project. > > > When you are doing conversion of an old project (struts, JSP, JSF, > > etc), the old way of measuring 'time' and 'size' are a little > > different with AJAX/GWT. > > > For example, this tool:https://addons.mozilla.org/en-US/firefox/addon/1743, > > really doesn't handle AJAX/GWT well. > > > Can anyone share any tools or experiences in showing the time/ > > bandwidth difference of an old application to a new application in > > either a (eventual) side-by-side per-screen, or 'per drive-through > > scenario' approach? > > > thanks! > > -D -- 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.
