Move mithril redraws to rafScheduler Mithril redraw executes once every 16ms, not once per animation frame. If a mithril redraw takes more than 16ms, we can end up with multiple redraws per animation frame. See mithril code here: https://github.com/MithrilJS/mithril.js/blob/v1_1_x/api/redraw.js Multiple redraw jank screenshot: https://screenshot.googleplex.com/97PPSGxh69D Devtools trace: http://bit.ly/2BG5oEN This CL moves mithril redraws to rafScheduler. rafScheduler now has scheduleRedraw and scheduleFullRedraw. In the animation frame callback, we want to do a synchronous mithril redraw. m.redraw.sync is available in tip of tree mithril, but not in the latest stable version 1.1.6. Until that's available, we use m.render to do the synchronous redraw. Since rafScheduler now runs mithril redraws, it can also directly run the canvas redraws right after, and we do not need CanvasRedrawTrigger to hook canvas redraws to mithril redraws. Change-Id: I06e42b1d6aa17dbef428b66d3f0d20f8fea7edfa
Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.
It consists of:
A portable, high efficiency, user-space tracing library
designed for tracing of multi-process systems, based on zero-alloc zero-copy zero-syscall (on fast-paths) writing of protobufs over shared memory.
OS-wide Linux/Android probes for platform debugging
Web-based frontend
A UI for inspection and analysis of traces (coming soon).
Batch processing of traces
A python / C++ (TBD) library for trace-based metrics (coming soon).

Perfetto is building the next-gen unified tracing ecosystem for:
The goal is to create an open, portable and developer friendly tracing ecosystem for app and platform performance debugging.
Designed for production
Perfetto's tracing library and daemons are designed for use in production. Privilege isolation is a key design goal:
See docs/security-model.md for more details.
Long traces
Pefetto aims at supporting hours-long / O(100GB) traces, both in terms of recording backend and UI frontend.
Interoperability
Perfetto traces (output) and configuration (input) consists of protobuf messages, in order to allow interoperability with several languages.
See docs/trace-format.md for more details.
Composability
As Perfetto is designed both for OS-level tracing and app-level tracing, its design allows to compose several instances of the Perfetto tracing library, allowing to nest multiple layers of tracing and drive then with the same frontend. This allows powerful blending of app-specific and OS-wide trace events. See docs/multi-layer-tracing.md for more details.
Portability
The only dependencies of Perfetto's tracing libraries are C++11 and Protobuf lite (plus google-test, google-benchmark, libprotobuf-full for testing).
Extensibility
Perfetto allows third parties to defined their own protobufs for:
Allowing apps to define their own strongly-typed input and output schema. See docs/trace-format.md for more details.