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.
Difference between revisions of "Trace Compass/Feature Roadmap"
(→Planned) |
|||
| Line 1: | Line 1: | ||
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. | 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. | ||
| − | == | + | == Released in [https://projects.eclipse.org/projects/tools.tracecompass/releases/1.0.0 1.0] == |
* Support for perf traces in CTF format | * Support for perf traces in CTF format | ||
| + | * Automatic vertical alignment of time-based views (Part 1 of [[Trace_Compass/Design_Documents/Aligned_x_axis | this document]]) | ||
| − | = | + | = Ready for 2.0 = |
| − | + | * Moveable/hideable event table columns | |
| + | |||
| + | = Planned for 2.0 = | ||
* Dependency analysis framework ([http://multivax.blogspot.ca/2013/12/system-level-profiling-of-apt.html example]) | * Dependency analysis framework ([http://multivax.blogspot.ca/2013/12/system-level-profiling-of-apt.html example]) | ||
| − | |||
* Virtual Machine analysis (See screenshots at the end of [http://www.tracingsummit.org/w/images/c/cd/Tracingsummit2014-gbastien.pdf this presentation]) | * Virtual Machine analysis (See screenshots at the end of [http://www.tracingsummit.org/w/images/c/cd/Tracingsummit2014-gbastien.pdf this presentation]) | ||
| − | |||
| − | |||
* Support for remote fetching of traces using remote profiles | * Support for remote fetching of traces using remote profiles | ||
| − | * Support for new features of recent versions of LTTng Tools in LTTng Tracer Control view | + | * Support for new features of recent versions (2.5+) of LTTng Tools in LTTng Tracer Control view |
| − | + | ||
| − | + | ||
| − | + | ||
* Latency Analysis | * Latency Analysis | ||
| + | * Support for arrows in data-driven time graph views | ||
| + | * Auto-filtering of inactive elements in time graph views | ||
= Wishlist = | = Wishlist = | ||
| Line 25: | Line 24: | ||
These features have been proposed and deemed interesting to have, but nobody has committed to work on them yet. | These features have been proposed and deemed interesting to have, but nobody has committed to work on them yet. | ||
| − | |||
| + | * Support for perf traces in standard perf.data | ||
* 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 | * Reduce the size of state system history files | ||
** 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 | * Support for data-driven Sequence Diagrams | ||
| − | |||
* Sequence Diagrams for PCAP traces | * Sequence Diagrams for PCAP traces | ||
| − | + | * Visually define data-driven state providers with state diagrams | |
| − | * | + | * [[Trace_Compass/Design_Documents/Aligned_x_axis | Aligned X axis (time)]] |
Revision as of 11:51, 15 July 2015
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.
Released in 1.0
- Support for perf traces in CTF format
- Automatic vertical alignment of time-based views (Part 1 of this document)
Ready for 2.0
- Moveable/hideable event table columns
Planned for 2.0
- Dependency analysis framework (example)
- Virtual Machine analysis (See screenshots at the end of this presentation)
- Support for remote fetching of traces using remote profiles
- Support for new features of recent versions (2.5+) of LTTng Tools in LTTng Tracer Control view
- Latency Analysis
- Support for arrows in data-driven time graph views
- Auto-filtering of inactive elements in time graph views
Wishlist
These features have been proposed and deemed interesting to have, but nobody has committed to work on them yet.
- Support for perf traces in standard perf.data
- Support for ftrace traces
- 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
- 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
- Sequence Diagrams for PCAP traces
- Visually define data-driven state providers with state diagrams
- Aligned X axis (time)