I'm seeing this as well. When I switch from embedded jetty to
noserver, everything is MUCH slower, despite being all local on the
same machine with PLENTY of RAM and CPU to spare. It's bad enough
that development time is severely impacted.
On Apr 1, 6:11 am, Skal pasvinc...@gmail.com wrote:
Hi all,
We are developping an application with many panels and remote services
(about an hundred) and we are facing a very annoying issue with the
oophm dev mode, the browser refresh time takes up 30 000 to 90 000 ms.
The -Dgwt.perflog jvm option shows that most of the time is spent in
the Oophm.SessionHandler.loadModule call (all the app is in a single
module). Also, we don't use the embedded jetty server (-noServer, we
use an another jetty server).
I notice that in dev mode, *.gwt.rpc and *.cache.png files are still
generated in the war directory after each refresh, even if the code
modification doesn't have an impact on this ressources (for example
just a label change), why that ?
I've heard about a rpc.blacklist property config extension, does it
make sense to use this property to block some remote service
compilation thus accelerating the refresh time ?
Thanks a lot for any clue.
--
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-tool...@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.
