Hi Daniel,

I made some more serious tests on a production project with which i used to 
develop using the classic DevMode.
Those are the numbers that come from the CodeServer with or without the 
-XcompilePerFile flag, and they are quite impressive :

   Standard Compile per file Reduction
1st compile  101s 41s  59%
Change 1 string and recompile 16s 5,8s  64%
Change 1 string and recompile 18s 3,6s  80%

First compile Unification traversed 60072 fields and methods and 6179 
types. 6139 are considered part of the current module and 6139 had all of 
their fields and methods traversed. 
Second compile Unification traversed 2528 fields and methods and 2650 
types. 124 are considered part of the current module and 124 had all of 
their fields and methods traversed.

I did not use the Chrome dev tools to debug the application but the SDBG 
plugin for Eclipse.
The experience is almost incredible, perfectly usable and much faster than 
the classic DevMode. The only bad thing is not having the Java fields 
inspected correctly (although one can guess the javascript equivalents most 
of the time) and little things that can be covered with time... Everything 
needs a compromise and having that debugging experience brought back to 
Eclipse is really what i was fearing to lose with the SuperDevMode. So i 
will adopt the SuperDevMode for a while !
Ray, Brian, John and Robert, Ivan, James and you all made a really 
impressive work ! The future of GWT is assured ! Now i can't wait to have 
the Java 8 features to be tried ;)

Now i have a question about the message "Unification traversed..." : first 
what means the message exactly (i need to see the code) and second why some 
many fields and methods are traversed if only change one file ?

Next i had ideas but no time to implement them, maybe i dump them here with 
the hope they can be useful ;)
- Recompile on file change. The time the user switches to the browser, the 
compile is almost finished.
- Tool to benchmark.
- Recompile on F5, standard SuperDevMode linker
- GWT plugin for eclipse : GWT tools + SDBG
- Sample including the experience

Thanks a lot again for all the work and the good things coming out !
Arnaud



Le lundi 1 septembre 2014 12:25:38 UTC+2, Daniel Kurka a écrit :
>
> Hi Arnaud,
>
> are those 10s after the changes we made or before?
>
> -Daniel
>
>
> On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER <[email protected] 
> <javascript:>> wrote:
>
>> Thanks to all of you who participated to this very good things !
>>
>> I am now able (from the trunk) to have a great experience debugging with 
>> Gwt + Eclipse + Sdbg + Chrome.
>>
>> I cannot be quantitatively very precise but the latest optimization 
>> (-XcompilePerFile) seems to give good results. My project on which i test 
>> that is not so big so the compilation takes about 10 seconds. Improvements 
>> are obvious !
>>
>> Thanks a lot!
>>
>> Le vendredi 29 août 2014 18:16:40 UTC+2, juan_pablo_gardella a écrit :
>>>
>>> Great news!! Thanks a lot for the effort.
>>>
>>>
>>> On 29 August 2014 13:02, Ivan Markov <[email protected]> wrote:
>>>
>>>> BTW using a more recent laptop seems to make a difference and nearly 
>>>> doubles the performance:
>>>> MacBook Pro model 2013 (I7 2.7 GHz):
>>>> - 2 to 3 seconds for recompiling changes to a single file
>>>> - 2 to 3 seconds for linking
>>>> - Changes to more types of course again results in a growth of the 
>>>> recompilation time; this time it is 8 instead of 13 seconds for the same 
>>>> set of around 10 changed files. Linking still 3 seconds.
>>>>
>>>> I think you are getting there!
>>>>
>>>>  -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "GWT Contributors" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to google-web-toolkit-contributors+unsubscribe@
>>>> googlegroups.com.
>>>>  To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/google-web-toolkit-contributors/c646cebb-005a-
>>>> 42fd-9f9d-62334e1a3189%40googlegroups.com 
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/c646cebb-005a-42fd-9f9d-62334e1a3189%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] 
>> <javascript:>.
>>  To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>  

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ecad7963-656b-48f2-b85e-ce56060359c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to