GWT RPC has been particularly offensive when it comes to being slow in
Chrome. If you're using RPC, try running GWT from SVN head. You should see a
massive improvement in Chrome performance.
On Fri, Jul 15, 2011 at 11:12 AM, Dennis Haupt d.haup...@googlemail.comwrote:
switching to dev mode took
it's the speed. not the execution speed, that one is good enough.
what i mean is the compilation speed. compiling my complete java project
takes 30 seconds. compiling the tiny gwt part of it takes 91 seconds.
activating the hosted mode takes about 1-2 minutes (didn't measure, feels
like it).
mmm I work in this manner. I use maven, but is the same.
1) Make the war (mvn package). Only the first time.
2) Start dev mode.
3) Open browser (I use IE, is the fastest in dev mode). Wait at first time a
minute.
4) Test the app and modify code.
5) Refresh page in IE. Wait 10s aprox.
6) Repeat 4)
There is a google IO session which covers speeding up the compile
process during development, it is in the second half of a talk on the
compiler in general.
http://www.youtube.com/watch?v=qT6ZsQBM7kY
Also, if you are working on client side code, a lot of the time you
don't need to go through the
On Fri, Jul 15, 2011 at 1:23 PM, Dennis Haupt d.haup...@googlemail.comwrote:
it's the speed. not the execution speed, that one is good enough.
what i mean is the compilation speed. compiling my complete java project
takes 30 seconds. compiling the tiny gwt part of it takes 91 seconds.
=activating the hosted mode takes about 1-2 minutes (didn't measure,
feels
like it). debugging like this takes forever.
Yep. Documentation says use this mode always during development, never
to compile.
Bringing up dev mode URL is taking time (with debug option).
Not sure selecting particular
I m pretty sure the GWT team is allready on making dev mode run even
faster.
I heard they are obsessed about speed @Google :)
But when you think about it a second what devmode does you will see that
performance is pretty good right now. I mean this is Javabyte code remotelly
manipulating your
This is because GWT compiles the javascript for all the browsers.. around 5
browsers - 10 permutations..
For the development mode, you can compile only for one browser. Ex: for IE,
use the below property in *.gwt.xml file
This would reduce your compile time..
--
You received this message
http://www.coderanch.com/t/480416/GWT/Improved-Compiler-Performance-GWT-Reduce
--
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/-/tW9IXgx_VHQJ.
To
For compiler speed, on development builds you can reduce the number of
permutations (restrict user agents, locales, etc)
I have a sample app here which does that:
https://bitbucket.org/magnomp/gradlegwt, but uses Gradle for build.
Anyway, most of the time you will be using devmode, not the
that helped most, thanks
2011/7/15 vinayak kulkarni bkvina...@gmail.com
This is because GWT compiles the javascript for all the browsers.. around 5
browsers - 10 permutations..
For the development mode, you can compile only for one browser. Ex: for IE,
use the below property in *.gwt.xml
switching to dev mode took 41 seconds, chrome became responsive again about
~30 seconds after that. gut feeling wins.
2011/7/15 Rob Coops rco...@gmail.com
On Fri, Jul 15, 2011 at 1:23 PM, Dennis Haupt d.haup...@googlemail.comwrote:
it's the speed. not the execution speed, that one is good
Chrome is slow in dev mode. Try firefox instead.
On 15/07/11 16:12, Dennis Haupt wrote:
switching to dev mode took 41 seconds, chrome became responsive again about ~30
seconds after that. gut feeling wins.
--
You received this message because you are subscribed to the Google Groups Google
just off topic. what is life cycle in dev mode?
Is it java byte code all the way to browser (plug in )? (I mean no
java script any where)
On Jul 15, 8:24 am, Paul Robinson ukcue...@gmail.com wrote:
Chrome is slow in dev mode. Try firefox instead.
On 15/07/11 16:12, Dennis Haupt wrote:
http://code.google.com/p/google-web-toolkit/wiki/DesignOOPHM gives a decent
overview and specs out the wire protocol.
High level:
The bootstrap page detects the ?gwt.codesvr= fragment, and tries to load the
plugin.
The plugin then validates the permissions. Assuming the permissions are
good, it
Dennis Haupt wrote:
that helped most, thanks
More on that here:
http://code.google.com/webtoolkit/doc/latest/FAQ_DebuggingAndCompiling.html#Can_I_speed_up_the_GWT_compiler?
The allowable values for user.agent are defined here:
16 matches
Mail list logo
