Hey Joe. Yea, I switched to using overlay types, which I probably should have used from the beginning. It's on the order of a thousand times faster.
Thomas, I see gwt-maven-plugin 2.5-rc1! I didn't realize you contributed to that project as well. Nice work, and very well done. -tjw On Saturday, July 14, 2012 3:34:29 PM UTC-4, Joseph Lust wrote: > > 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/-/sa8J3HTwZKUJ. 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.
