Re: Measuring effect of using GWT features on compile time

On Wednesday, June 8, 2016 at 1:50:03 AM UTC+2, jgindin wrote:

I'm looking for some way to see how much of my GWT compile time is coming from our usage of different features. Specifically:

• UiBinder
• RPC
• Guice (not core GWT, I know...but maybe there's a way to see this too)

For RPCs in particular, I've tried to dig around and see if there are any "hidden" flags, but have come up empty handed so far.

Does anyone know of some way to find this information? (I'm using GWT 2.7...)

You'll get timing information for each generator invocation when you set the log level to DEBUG, but it won't be easy to parse.

But there are hidden flags (as system properties) to enable performance logging; e.g. -Dgwt.speedtracerlog=/path/to/file.html (but this requires the SpeedTracer extension for Chrome, which is no longer maintained –probably no longer works– and has been removed from the Chrome Web Store), or -Dgwt.dashboard.notifierClass=xxx (where xxx is the name of a class implementing com.google.gwt.dev.util.log.dashboard.DashboardNotifier). That last one is what (I believe) Google is currently using internally. You'll get specialized events for UiBinder, RPC and GIN (and I18N), and a generic event for other generators. (you'll find -Dgwt.perflog and -Dgwt.perfcounters but I don't think they produce anything nowadays)

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.