This is a well known issue. Of course it is because the browser plugins intercept all JS code and run it in the DevMode plugin (in Java) and then pass the result back to the browser. While Java code is fast, the overhead of the passing back and forth slows things down. Do something several thousand times and it becomes very noticeable.
As the docs point out<https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging#DevGuideProdMode>, in DevMode, some things that might be slow in JS will run fast (in Java), while other things that run slow in DevMode will actually run fast (i.e. deserialization) in Prod mode. The work around I use (since my app deserializes ~15K objects), is to use a mock service in DevMode that only returns a few hundred results. This works well for fast debugging, and then when I run in Prod mode, I get the actual service and all 15K objects. For comparison, it was taking 45000ms to deserialize in DevMode and 100ms in ProdMode for 15K objects. Hope that helps, Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/sGt8BTL-g10J. 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.
