Re: GWT 2.7 SuperDevMode Compile Times

Interesting. We're also using GIN and UiBinder, but also GWT-RequestFactory with editors/drivers. So lots to things to be generated.

Also wondering how to split client and server into different mvn modules when using ReqFactory - @ProxyForName and @ServiceName should work for class names, however they still require a class reference to the server-side Entity/Service locator.

On Monday, April 3, 2017 at 4:29:02 PM UTC+8, Jens wrote:

Things I would try:

• GWT 2.8; SDM will likely be faster
  
• removing server-side dependencies from GWT classpath; which means with Maven splitting client and server code into separate modules.

I guess it won't really help. We are in the same situation using some custom GWT build between 2.7 and 2.8. I think the real problem is the combination of UiBinder, GWT-RPC and Google GIN. Our recompile times on simple changes are always about 8-12 seconds and linking time roughly 5 seconds (SSD doesn't really help here) so we usually end up with something around 15 seconds. 

I would really like to see some profiling output of GWT compiler but given that SpeedTracer is kind of dead I have no idea if there is an alternative to visualize the result.

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.