I have about 250kloc, lots of RPC and no generators or UI binder.

With decent hardware, a recompile is about 7-8 seconds. With a 3-4 year old 
computer, it was taking about 20 seconds.

Paul

On 14/11/12 14:34, Paul Stockley wrote:
> Our project is about 35,000 lines of client and server code. We don't use RPC 
> or request factory because we have our own RPC mechanism. We do have quite a 
> lot of UI binder files. Super dev mode recompiles take between 6 to 8 
> seconds. So it sounds like the generators are your problem. For some types of 
> generators, they run every compile even if you haven't changed any related 
> code. They are aware of the issue and will be looking into it for a future 
> release.
>
> On Wednesday, November 14, 2012 3:24:35 AM UTC-5, StefanR wrote:
>
>     In a larger GWT multi project app and it took me several hours to get the 
> new SuperDevMode running (I found this video 
> <http://jeff-davis.blogspot.de/2012/07/setting-up-gwt-25s-superdevmode.html> 
> very helpful).
>     Now, I'm a bit disappointed about the coolest new feature of 2.5 and I 
> wonder if I have missed something.
>
>       * Compilation is slow. It takes between 1 and 2 minutes plus the 
> bootstrap time of my server app. The app has sth above 20k LOC and heavily 
> uses RequestFactory and GIN code generators, maybe that's the reason? So 
> overall startup performance is worse than with standard DevMode.
>       * Code changes require a recompile. In DevMode non-structural changes 
> are applied automatically by the Eclipse Debugger.
>       * Debugging the code in the Browser is ... hm, it works. But honestly, 
> nothing compare to a IDE debugger. Browsing through the source tree in Chrome 
> is a pain with thousands of classes.
>       * GWT CodeServer is very resource intensive. During compilation, I 
> cannot use my machine for anything else. If it's running it takes more than 
> 1GB of RAM.
>
>     Is anyone successfully using SuperDevMode for larger apps?
>
> -- 
> 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/-/q1lGr7hhCo4J.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-web-toolkit?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to