DevTools performance

[tbranyen]

One problem with the current design approach is that we want to show one row per transaction. In the case of 60fps requestAnimationFrame renders, we cannot possibly show all of them, even with virtual pagination.

Scratchpad thoughts:

• Could limit the amount we show to always be the last 50, or some configurable setting?
• Only send over the bare minimum data, such as just stat numbers
• Could we provide only deltas of the oldTree and newTree to save on transfer cost?
• Maybe leverage a "record" button for profiling the extra data, that way its intentional that you want it collected for memory/cpu reasons
• Maybe treat it like kibana? Force the user to write a query against the dataset and then display the results...