Re: Analyzing which GWT modules are taking more memory during GWT compile

You can not know that. It is a single AST for your complete application, its not an AST per GWT module. GWT gathers all source files that are visible through all referenced GWT module's <source path="..."/> tags. Then it parses this source files starting with your EntryPoint. At this point GWT modules are irrelevant to the GWT compiler.

The only thing you can do is providing more RAM to the compiler (or try GWT trunk, maybe there are already some memory usage optimizations implemented). But at the end.. the larger your app, the more RAM you need.

-- 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+unsubscribe@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/groups/opt_out.