I hadn't noticed
http://code.google.com/p/google-web-toolkit/wiki/LightweightMetricsDesignuntil
someone pointed it out earlier. Should give you a way of gathering
some rough idea of RPC performance.
On Wed, Apr 15, 2009 at 10:18 PM, Sumit Chandel wrote:
> Hi Russell,
> To reinforce Vitali's poin
Hi Russell,
To reinforce Vitali's point, you're not likely to gain much about how your
application will perform for your users by profiling it in hosted mode. For
most performance hot spots, testing the application and using it in the
hosted mode browser should be more than enough to sound the alar
I'm not sure why it is running slow either. After the brief time that
I have tried to look at it thus far, it seems that memory seems
somewhat ok (in my browser, it sits at 160-170mb usage, and only
really goes up if you generate graph after graph after graph really
fast, but it does go back down
Well I not sure if this is the case for you or not. In my workflow
program I did not use rpc and gotten data with json.
The workflow program the data from the json is huge and the program
became really slow when I am reading the json data into a new class.
What I ended up doing is the class just
Profiling in hosted mode is kind of a waste of time since there's a lot of
expensive stuff that happens that's hosted-mode specific. You have to be
really careful & fully understand how GWT works in hosted mode to be able to
glean any kind of meaning. And even then, it's meaningless because the
b
I have gotten to the point where I would like to profile my app to see
why it is running slow, but I'm not quite sure where to begin.
I would like to be able to first profile in hosted mode (and later use
a Javascript profiler in web mode).
I found a profiler called TPTP that seems to be somewha
