Nice! But just FYI, I'm not sure how up to date the loggings in the compiler are so the results might be misleading.
On Mon, Apr 24, 2017 at 5:07 PM, Jens <jens.nehlme...@gmail.com> wrote: > I stumbled upon opentracing.io some time ago and while it is primarily > designed to trace distributed services you can also use it to trace a > single process obviously. > > GWT compiler can produce speedtracer logs but you can not easily visualize > them because the Chrome plugin does not work anymore. So I thought I give > it a try and as a POC I have changed the implementation of the current > speedtracer event API inside GWT compiler to record timings using > opentracing.io API (just wanted to avoid updating lots of call sites). As > a result I can now start SuperDevMode using some JVM system parameters like > > -Dgwt.opentracing.tracerImpl=com.example.tracing.zipkin.ZipkinOpenTracingTracer > (without it a NoopTracer will be used) > -Dzipkin.url=http://localhost:9411/api/v1/spans > -Dzipkin.serviceName=SuperDevMode > > and launch a Zipkin server > > docker run -d -p 9411:9411 openzipkin/zipkin > > (or any other opentracing.io compatible server that stores and visualizes > the timing information. You would need to implement a different Tracer then) > > Now every time SDM compiles, all speedtracer events are converted into > opentracing.io spans and you get some visualization like: > > > <https://lh3.googleusercontent.com/-nbdgporQ93k/WP6QOZqFJvI/AAAAAAAAAL0/k6ItTrleRagiEMwJBnyk5bf5U2Q-6eMOACLcB/s1600/zipkin.png> > > > There are some rough edges to be solved, like a single recompile results > in multiple traces not yet connected to each other, but I though I'll just > share this quick POC with you. > > Given the future of GWT 2.x I am not sure if it is worth investing more > time in it but at least it shows that a relatively easy migration would be > possible to some newer (standard) tools to visualize compiler timings > again. So if we want to make speedtracer logs useable again this might be > an option. > > > -- 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/f60836a4-4fa9- > 4d4a-b2db-182f8c1e3e38%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/f60836a4-4fa9-4d4a-b2db-182f8c1e3e38%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 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/CAN%3DyUA21_%2B64sw1q5xPVezzR%3DwYseuak_9mxx6UK6wLCHdjaGw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
