Starting super dev mode in debug : performance very bad

[Julien Dramaix]

Hi,

I've tried to run the super dev mode (dev mode with flag -superDevMode) in debug in order to debug my server side code. The problem is that the superdevmode server is also started in debug mode and the time needed for the initial compilation is very very bad. This is an example of time needed by the first compilation with a small application:

       

Linking per-type JS with 3891 new types.

               prelink JS size = 8177175

               prelink sourcemap = 8177175 bytes and 194766 lines

               postlink JS size = 8054573

               postlink sourcemap = 8054573 bytes and 191812 lines

            Source Maps Enabled

         Compile of permutations succeeded

         Compilation succeeded -- 418,016s

      Linking into /var/folders/qc/ktqtdtdx6790j436xz3jqw3r0000gn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/war/kaam; Writing extras to /var/folders/qc/ktqtdtdx6790j436xz3jqw3r0000gn/T/gwt-codeserver-5506406643949710211.tmp/com.caerus.kaam.KaamSdm/compile-3/extras/kaam

         Link succeeded

         Linking succeeded -- 10,692s

      430,813s total -- Compile completed

If you don't change anything to the code and recompilation of the application takes 2,147s.

For your info, the same application running not in debug mode takes 20s for the initial compilation.

That makes simply the debug mode impossible to use and you are not able to debug your server side code anymore. The workaround is to run two separate processes, one with -superDevMode and --nostartServer flags and another without the -superDevMode flag that you can start in debug mode.

I don't know if we can do something on the superdevmode side, maybe the solution can come from the IDE directly where the superdevmode process is never launched in debug mode ?

Any thought ?

Julien

PS: I'm using Intellij13

[John Stalcup]

Hey

I don't think there's anything special we're doing that would be particularly slow in a JVM debugger.

Maybe this is a stupid question but, do you have any conditional breakpoints set? Those can be particularly slow. Also maybe the debug process costs extra RAM, putting the JVM at it's RAM limit, then causing a lot of really slow GCs? You could try raising the RAM.

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7DgGmkkQVe3mQgXxT%2B7rjbM%2BMOCv7TVjRPa08h%3DDPiEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Julien Dramaix]

yep sorry, that was due to a old breakpoint I've put in the ClientBundleGenerator...

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ8tiSVZPm5XV08TPK%3Dm6v6cKxdFeLZ0QUZ_iYHPGTZcBA%40mail.gmail.com.