2010-11-25 Francois Chouinard <fchouinard@gmail.com> Fix for Bug331156
[deliverable/tracecompass.git] / org.eclipse.linuxtools.lttng.help / html / limitations / limitations.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
2 <HTML>
3 <HEAD>
4 <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
5 <TITLE>Limitations</TITLE>
6 <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.1 (Linux)">
7 <META NAME="CREATED" CONTENT="0;0">
8 <META NAME="CHANGED" CONTENT="20091008;18193600">
9 </HEAD>
10 <BODY LANG="en-CA" DIR="LTR">
11 <H1>Limitations</H1>
12 <P>The current implementation is still under heavy development and
13 some important features are still missing.<BR>Here is a list of the
14 known bugs and missing features that are worked on.</P>
15 <UL>
16 <LI><P STYLE="margin-bottom: 0cm"><B>Thread issues affect
17 performance</B></P>
18 <P STYLE="margin-bottom: 0cm; font-weight: normal">The multi-thread
19 access to the traces is mostly turned off for now so the user might
20 experiment a very long load time when opening a trace and/or
21 zooming. Of course, this is especially true for big trace.</P>
22 <P STYLE="margin-bottom: 0cm"><SPAN STYLE="font-weight: normal">In
23 the future, the traces with be opened and indexed asynchronously,
24 with the result of greatly improved performance.</SPAN></P>
25 </UL>
26 <P STYLE="margin-bottom: 0cm"><BR>
27 </P>
28 <UL>
29 <LI><P STYLE="margin-bottom: 0cm"><B>No support for individual traces</B></P>
30 <P STYLE="margin-bottom: 0cm">The code for loading and parsing an individual
31 trace (not part of an experiment) is currently disabled. As a workaround,
32 just create an experiment with the single trace you want to analyze.
33 </P>
34 </UL>
35 <P STYLE="margin-bottom: 0cm"><BR>
36 </P>
37 <UL>
38 <LI><P STYLE="margin-bottom: 0cm"><B>One trace per experiment is
39 currently supported</B></P>
40 <P STYLE="margin-bottom: 0cm">Work to be able to merge and index
41 several traces into a single experiment have not being completed
42 yet.
43 </P>
44 <P STYLE="margin-bottom: 0cm">In the future, it will be possible to
45 process several traces at once and to compare them in the views.</P>
46 </UL>
47 <P STYLE="margin-bottom: 0cm"><BR>
48 </P>
49 <UL>
50 <LI><P STYLE="margin-bottom: 0cm"><B>Time Frame View</B></P>
51 <P STYLE="margin-bottom: 0cm">In some cases, the End Time of the Time
52 Frame view is not set correctly (symptom: the nanoseconds are identical
53 to the Start Time nanoseconds and the Interval nanoseconds = 0).
54 <P STYLE="margin-bottom: 0cm">
55 To set it properly, just spin up the End Time seconds field.
56 </UL>
57 <P STYLE="margin-bottom: 0cm"><BR>
58 </P>
59 <UL>
60 <LI><P STYLE="margin-bottom: 0cm"><B>Simultaneous data requests</B></P>
61 <P STYLE="margin-bottom: 0cm">All views are currently working on a
62 standalone basis. Therefore, time selection synchronization among
63 views does not trigger simultaneous data requests, which heavily
64 hurts the performance of the application.
65 </P>
66 <P STYLE="margin-bottom: 0cm">In the future, data request will be
67 centralized in the application, resulting in better response time in
68 and between views.</P>
69 </UL>
70 <P STYLE="margin-bottom: 0cm"><BR>
71 </P>
72 <UL>
73 <LI><P STYLE="margin-bottom: 0cm"><B>No trace recording capability
74 in Eclipse yet</B></P>
75 <P STYLE="margin-bottom: 0cm">It is not currently possible to record
76 a new trace directly in Eclipse, an user that would like to record a
77 new trace would need to use external tools, like LTTv.</P>
78 <P STYLE="margin-bottom: 0cm">In the future, a &ldquo;Control view&rdquo;
79 will be provided for the user to allow him to easily a new trace
80 inside Eclipse. It should also be possible to start the recording on
81 a remote host from that view.</P>
82 </UL>
83 <P STYLE="margin-bottom: 0cm"><BR>
84 </P>
85 <UL>
86 <LI><P STYLE="margin-bottom: 0cm"><B>Experimental Multi-CPU support</B></P>
87 <P STYLE="margin-bottom: 0cm">Although working, some more work need
88 to be done on trace that handle multiple processors. It is reputed
89 to work already but this feature is mostly untested for now.</P>
90 <P STYLE="margin-bottom: 0cm">In the future, multi-CPU should be
91 supported and work as well as uni-CPU traces.</P>
92 </UL>
93 <P STYLE="margin-bottom: 0cm"><BR>
94 </P>
95 <UL>
96 <LI><P STYLE="margin-bottom: 0cm"><B>Experimental 64 bits and/or non
97 x86 architecture implementation</B></P>
98 <P STYLE="margin-bottom: 0cm">The code used to read and parse files
99 have not been extensively tested on 64 bits and was not tested at
100 all on architecture different than x86 computer. The code is
101 believed to work on a broad horizon of architecture but this cannot
102 be certified for now.</P>
103 <P STYLE="margin-bottom: 0cm">In the future, all x86 (32 and 64
104 bits) as well as all PPC (32 and 64 bits) should work and possibly
105 some (all?) models of SPARC.
106 </P>
107 </UL>
108 <P STYLE="margin-bottom: 0cm"><BR>
109 </P>
110 <UL>
111 <LI><P STYLE="margin-bottom: 0cm"><B>Missing filters and ordering on
112 all views</B></P>
113 <P STYLE="margin-bottom: 0cm">There is currently no way to filter
114 events following some criteria or to dynamically sort the different
115 fields.
116 </P>
117 <P STYLE="margin-bottom: 0cm">In the future, both should be
118 implemented.
119 </P>
120 </UL>
121 <P STYLE="margin-bottom: 0cm"><BR>
122 </P>
123 <UL>
124 <LI><P STYLE="margin-bottom: 0cm"><B>Some views missing and/or need
125 more work</B></P>
126 <P>Some more views (&ldquo;Control&rdquo;, &ldquo;Histogram&rdquo;,
127 etc...) are currently missing but planned in the Eclipse
128 implementation and some others (&ldquo;Statistics&rdquo;) are
129 working but need more work to be brought were they need to be.<BR>In
130 the future, all views provided by LTTv will be supported in Eclipse
131 and more!</P>
132 </UL>
133 <P><BR><BR>
134 </P>
135 </BODY>
136 </HTML>
This page took 0.03556 seconds and 5 git commands to generate.