These outputs are normal when you enable DEBUG log level. It basically 
shows you what GWT does during deferred binding rules matching. Yes its a 
lot of output.

Generally as your app grows you also have to adjust the heap memory during 
compilation from time to time. The -localWorkers option also increases ram 
usage during a compile (SDM probably always uses -localWorkers 1 as it only 
compiles a single permutation). Also applying all optimizations might cost 
additional memory (SDM does no optimization).

So if you have not discovered a compiler bug which causes the heap to go 
wild it is normal to give your compiler quite a bit of ram and that you 
have to increase it over time. You can use jvisualvm from Java to connect 
to the compile process and watch its heap usage during compilation.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to