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)
Line 17: Line 17:
 
* Support for perf traces
 
* Support for perf traces
 
** There is some ongoing work to make perf output directly in CTF
 
** There is some ongoing work to make perf output directly in CTF
 +
 
* Support for ftrace traces
 
* Support for ftrace traces
 
** Documentation at https://www.kernel.org/doc/Documentation/trace/ftrace.txt
 
** Documentation at https://www.kernel.org/doc/Documentation/trace/ftrace.txt
 
** Investigate if we could re-implement the KernelShark view using a generic time graph view
 
** Investigate if we could re-implement the KernelShark view using a generic time graph view
 +
 +
* 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).

Revision as of 15:45, 30 October 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

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).

Back to the top