Tuesday, June 19, 2012

Re: Debugging is terribly slow



On Wednesday, June 20, 2012 6:41:36 AM UTC+2, Magnus wrote:


Am Dienstag, 19. Juni 2012 17:19:26 UTC+2 schrieb Thomas Broyer:

Have you tried SuperDevMode? Experimental and requires a bleeding-edge GWT version, if it helps being productive then it's probably worth the try.

Not yet. Where can I get more information on this?

Have a look at these:
 

Have you modularized your app so you can run only a subset of it in DevMode?

My app is modularized in packages, but I think this doesn't reduce the overhead when it is run. What level of modularization do you mean?

I mean creating GWT modules, and a few additional modules with an EntryPoint that you can use for development. For instance, a module that only contains a handful of "screens". Make sure you really modularize your app, so that these modules have a smaller "source path" (as defined by <source path=""/> in your modules) than your full app.
 
 
Have you tried profiling DevMode and tweaking the JVM options?

No! Which JVM options could I try?

Memory options to being with.
You can use -XX:+UseCompressedOops if you're using a 64bit JVM.

--
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/-/J7Fq5IJ8hB4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate