Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Trace Compass/Feature Roadmap"

(Planned)
(Wishlist)
Line 26: Line 26:
 
** Timestamps (2x 64 bits) are repeated for every single interval. Low-hanging fruit (using protocol buffers?)
 
** Timestamps (2x 64 bits) are repeated for every single interval. Low-hanging fruit (using protocol buffers?)
 
** Compress often-used values (including strings).
 
** Compress often-used values (including strings).
 +
 +
* Support for data-driven Sequence Diagrams

Revision as of 07:54, 14 November 2014

This page is meant to track all the higher-level planned features and feature requests. As features get implemented, we could move them to "Targeted for version x.y" and "Delivered in version x.y" sections. It would always track the "current" roadmap, but over time would also become a history of which feature was delivered in which version.

Planned

These features have people currently working on them, but no set release date yet.

  • Dependency analysis framework (example)
  • Configurable event table columns
  • Virtual Machine analysis (See screenshots at the end of this presentation)
  • Describe data-driven filters and high-level states
  • Visually define data-driven analysis with state diagrams
  • Support for remote fetching of traces

Wishlist

These features have been proposed and deemed interesting to have, but nobody has committed to work on it yet.

  • Support for perf traces
    • There is some ongoing work to make perf output directly in CTF
  • Reduce the size of state system history files
    • Timestamps (2x 64 bits) are repeated for every single interval. Low-hanging fruit (using protocol buffers?)
    • Compress often-used values (including strings).
  • Support for data-driven Sequence Diagrams

Back to the top