GWT - So terribly slow that makes development hard ... very hard ... extremely hard ...

[Ani]

Now that we have been using GWT for a while ... what do you think? Was it the right choice or thinking of migrating to other framework?

[Juan Pablo Gardella]

Hi,

Are you using the same server to run backend and front end? It is very useful use two servers. Take a look at https://github.com/tbroyer/gwt-maven-archetypes.

Juan

2013/4/18 Ani <anic...@gmail.com>

Now that we have been using GWT for a while ... what do you think? Was it the right choice or thinking of migrating to other framework?

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[tinnitus007]

Are you using Firefox?  If so, there's an issue: https://code.google.com/p/google-web-toolkit/issues/detail?id=7648

If not, I can report that SSD drives make a huge difference in GWT dev  mode.

[Paul Stockley]

performance improvement definitely seems to be an immediate priority. See the draft roadmap

https://docs.google.com/document/d/1bmp0a-d5cb_Sqb4w9rZyfMhg7i6lYfLLt3zymIFoAmo/edit

[Philippe Lhoste]

On 18/04/2013 19:22, Ani wrote:
> Now that we have been using GWT for a while ... what do you think? Was it the right choice
> or thinking of migrating to other framework?

Where is it slow?
In production?
Only in development mode?
The latter needs a quite efficient computer with good CPU and lot of memory, I fear.

Perhaps also take a look at Vaadin: it is GWT with a pre-compiled GWT, so it should be
more reactive at this level: I made a little demo application on an old, slow computer
without problem! (while a colleague was sweating and swearing on a similar computer with
SmartGWT...).

--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --

[emurmur]

Ani, here is what I see for compile times when I use super dev mode.

Release build (full GWT compile, 6 permutations); 3 minutes.

Starting the super dev mode code server (which does an initial compile): 60 seconds.

Compile using DevMode On bookmarklet in browser; 10 seconds.

So, in the morning I start the code sever (60 seconds) and leave it running all day.  From then on, when I change code in Eclipse, I switch to Chrome, run the bookmarklet (10 seconds) to compile it, then debug the Java using source map in Chrome Dev Tools.

The bookmarklet compiles a single permutation with reduced number of optimizations, so it is very fast.  Overall it's a nice workflow.  It's a lot like a JavaScript workflow, except you get a great IDE, tooling and type checking.

One thing to know about my project is that I'm doing low level browser coding using GWT.  I've written my own framework.  I don't use GWT widgets.  I don't use UIBinder, which uses a GWT Generator (I believe).  My understanding is that generators are very slow when used with Super Dev Mode because they run each time the bookmarklet compile is done.

I hope that helps.

Ed

On Fri, Apr 19, 2013 at 7:54 PM, emurmur wrote:

We are using GWT and it is performing very very well.  We use SuperDev mode.  We have no generators of any kind (I'm told generators can slow down SuperDev mode compiles considerably).  Our code/compile/debug cycle is very fast.  Doing a release build is pretty slow, but that does not happen very often.  We are very productive with it (and so we are happy).

Ed

 

On Thursday, April 18, 2013 10:22:15 AM UTC-7, Ani wrote:

[Patrick Tucker]

Do you increase the number of workers when you compile?

The arg is localWorkers. I specify 6, 1 for each permutation, that along with a memory spec of 1 gig and my compiles finish in just over a minute.

[Jim Douglas]

It's very hard to tell you anything useful when you post such a vague
comment.

What specifically is slow for you? How big is your application? How
powerful is your development computer?

On my MacBook Pro, I rarely bother with DevMode any more; I can do a
full compile of 6 permutations of my application (about 150,000 lines
of client-side Java source code) in just over 60 seconds. So I make a
batch of changes, and the recompile is done before I can fetch coffee,
and I'm ready for testing on multiple devices.

[Michael Prentice]

What version of GWT are you using? Have you done anything with your settings to improve performance of the compiler? There are a lot of documents, slides, and videos that cover this. Have you used SuperDev mode?

Your post is lacking of any real content and almost looks like trolling.

On Thursday, April 18, 2013 1:22:15 PM UTC-4, Ani wrote: