[ Tracking Issue ] Observatory -> DevTools Migration

[bkonyi]

Tracking issue for the Observatory migration effort.

Performance + Size Issues (P1)

• DevTools is an order-of-magnitude too big #4791 (p5)
• Audit performance of the various DevTools screens and components #5091 (p4)

Core Functionality

• Replace the DevTools trace viewer with the Perfetto UI #4207
• DevTools should be able to display Metrics populated via dart:developer. #3859
• DevTools debugger pane should display basic code coverage details #3862
• DevTools debugger should support keyboard shortcuts for stepping #3867 (p5)
• Add general support for jump to source #3869
• Improve readability of deep profiles #3874
• DevTools CPU profiler pane functionality should be on-par with Observatory #3861 (p2)

Advanced Functionality

• DevTools should display GC and native memory allocation statistics in the memory pane #3860
• Bring Observatory timeline features into DevTools timeline #2210
• Provide way to inspect Dart GC Roots / Object Store #3878
• Support program structure object exploration #3910

[kenzieschmoll]

Do we have usage metrics from Observatory on any of the missing features so that we can prioritize which ones we work on first? Or decide if any tools should be left out completely if users hardly use them?

[bkonyi]

Do we have usage metrics from Observatory on any of the missing features so that we can prioritize which ones we work on first? Or decide if any tools should be left out completely if users hardly use them?

Unfortunately not. I'm going to go through advanced features with the VM team (maybe some engine folks) to see what they use and would want migrated. There's already some features (e.g., Observatory's heap map) that we won't bother migrating.

So far I've only created issues for features that are actually useful or extend existing functionality (I'm sure I'll have more filed tomorrow).