Tracing V2: try out proto JS decoders for TraceViewer |
|||||
Issue descriptionBackground context: bit.ly/TracingV2 Once we have some prototypes of proto-based trace, we can write the auto-generated JS stubs for TraceViewer and see how they work. What we want to asses here is: 1. Do they work. 2. How fast are they compared to the current JSON. 3. How many events can we load before OOM-ing compared to the current JSON? In the meantime you want to start getting familiar with proto3 JS generation.
,
Oct 5 2016
,
Nov 25 2016
,
Jan 4 2017
,
Jul 19 2017
1. I've tried official JS protobuf implementation https://github.com/google/protobuf but it's complex to be integrated with TraceViewer primarly because of 'goog' imports in the library. 2. Realised that writing simple protobuf decoder is not that hard in JS. Bacause for purposes of Tracing V2 we gonna need to parse relatively small messages into JSON structures. It can be achieved by very simple message descriptors to be generated by protoc plugin. As an example I wrote trivial proof-of-concept https://github.com/gkraynov/open_source_snippets/tree/master/protobuf_javascript_trivial_decoder I think own implementation could be integrated with TraceViewer at lower cost and with better fit to the purpose. 3. Archiving the issue for this time because Tracing V2 is currently suspended, but somehow answering this question was important for planning. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by petrcermak@chromium.org
, Oct 5 2016