Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Jens]

>
> We just finished fixing a couple of issues in this compile mode (one 
> around JSOs and a couple around rerunning Generators).
>
> Any more feedback you have would be appreciated. If you see any bugs 
> please report them.
>

Just tried it yesterday. Compile time of normal SDM was about 40-50 seconds 
and with per-file it dropped down to 17-20 seconds when changing a single 
file. From this 17-20 seconds it was about 5-8 seconds pure compilation and 
the rest was linking. Since I use an SSD I don't think linking was limited 
by IO. I tried using -Dgwt.speedtracerlog but it seems like recompilation 
using per-file does not emit any speedtracer log, only the first precompile 
does so.

During the initial precompile there was a warning about certain css files 
loaded via class loader, although I am not sure why these few files caused 
the warning. These css files were referenced using @Source of CssRessource 
and had a relative path. Other css files did work fine. Also a warning 
about source maps was emitted (Unable to find all source code needed by 
debuggers, X files form source maps weren't found).

So in general it seems to work well however linking slows it down quite a 
bit.

-- J.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/b754c836-12ed-44c7-99fa-abb41b8c9373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Jens]

Ok just tried it again today with latest trunk and single file changes 
caused recompiles of 3-6 seconds depending on the file usage while linking 
stays relatively constant at 5-6 seconds. So linking seems twice as fast 
now, probably because less work will be done as a log statement "writing 
source maps and extras" is now missing.

During precompile SDM logs that it has traversed about 14 fields + 
methods and about 13000 types so you get an idea of the app size.

I think I will try using SDM with per-file compilation today to see how it 
works when I change multiple files etc.

-- J.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/3b0ced0e-4087-4107-8282-c1434c196516%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Ivan Markov]

I can confirm similar results to the previous post:
- 3 to 6 seconds for recompiling changes to a single file
- 5 to 6 seconds for linking
- Changes to more types naturally cause the compile time to grow (e.g. 13 
seconds for around 10 changed files) however the linking stays at 5 to 6 
seconds

The improvement compared to my original post seems to be:
- 50% to 100% for a single file recompile
- 300% to 400% for the linking phase

The machine is an ageing core I7-2630QM

Regarding project size, SDM reports traversal of 76197 fields and methods 
and 6950 types.

As for bugs, I don't have anything to report, but I was not using 2.7 on a 
daily basis yet.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/415d940f-071b-4e37-99d7-1c88a0df437c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Ivan Markov]

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+unsubscr...@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.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Juan Pablo Gardella]

Great news!! Thanks a lot for the effort.


On 29 August 2014 13:02, Ivan Markov  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+unsubscr...@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
> 
> .
>
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFsckH3PPtw8ACwCPeJ%2BMecmyOr1vRLVsMOQ_C_VfM7HyiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] -XcompilePerFile feedback

[Julien Dramaix]

Dear GWT team,

I'm now using the GWT 2.7 snapshot and I'm testing the "per file"
compilation and I found one issue.

Consider a UiBinder template using an external ClientBundle containing a
GssResource. If you change something on the .gss file and hit the button to
recompile the application. The application fails to run with this error:
Uncaught com.google.gwt.event.shared.UmbrellaException: Exception caught:
Exception caught: (ReferenceError) : HomePageView_BinderImpl$Widgets_1_g$
is not defined

To reproduce this error, use this small application:
https://github.com/jDramaix/gwtpgwt27, change something in
the file be/jdramaix/test/client/resources/style.gss and recompile the
application.

I found also two others issues, but I was not able to reproduce them with
the simple application. I will try to investigate Monday in order to get
you an example.

Julien

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D63%3D4dAGGLf3M-izC55GmE4Lr7i50FxW408Ye6P5G8JzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.