Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354272 - [LTTng] Latency analysis - tmf broadcast of event doesn't work
Summary: [LTTng] Latency analysis - tmf broadcast of event doesn't work
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francois Chouinard CLA
QA Contact: Francois Chouinard CLA
URL:
Whiteboard:
Keywords:
Depends on: 302489
Blocks: 331467 355141
  Show dependency tree
 
Reported: 2011-08-09 12:19 EDT by Mathieu Denis CLA
Modified: 2022-01-13 14:53 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Denis CLA 2011-08-09 12:19:22 EDT
Build Identifier: 20110526-1053

The tmf inter-component communication is not working with the latency view.

Reproducible: Always

Steps to Reproduce:
1.Open the latency analysis view and the histogram
2.Open a trace
3.The latency analysis view gets updated after the histogram, not at the same time.
Comment 1 Francois Chouinard CLA 2011-08-09 20:01:43 EDT
I don't think that this has to do with inter-component communication...

Historical recap: The original authors of the Latency Analysis/View opted for a scheme that required 2 passes over the trace. The first pass was used to collect some statistical data over the whole trace, while the second pass was used to properly populate the underlying data structure (and then the viewers).

At the time, the authors didn't have a good one-pass solution for this problem and we agreed that 2 passes was acceptable as a temporary solution. It was understood that we would have to re-work this part before committing the work to Open Source.


It is very likely that the first pass is performed (coalesced) at the same time as the Histogram View is built (and the Experiment is indexed, and the State System is built, and etc, etc, etc).

I believe that the Latency View can be revisited to make it a 1-pass analysis. We can probably re-use some of the work that was done for the Histogram View where the view was decoupled from the model and the buckets are now managed dynamically (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=352885).
Comment 2 Mathieu Denis CLA 2011-08-18 14:22:53 EDT
Moved to 355141
Comment 3 Mathieu Denis CLA 2011-08-18 14:27:02 EDT
moved to https://bugs.eclipse.org/bugs/show_bug.cgi?id=355141