Return-Path: Message-ID: <54D9BB0C.4040408@voxpopuli.im> Date: Tue, 10 Feb 2015 03:02:20 -0500 From: Alexandre Montplaisir MIME-Version: 1.0 References: <54C215D6.1030804@huawei.com> <54C2770F.4080305@voxpopuli.im> <54CC80CA.2020603@huawei.com> <54D2800B.3050808@voxpopuli.im> <54D582E9.4010709@huawei.com> <54D59F4B.4060608@voxpopuli.im> <54D5BDCD.5040407@huawei.com> <54D914D0.6000206@voxpopuli.im> <54D98F3A.8020202@huawei.com> In-Reply-To: <54D98F3A.8020202@huawei.com> Content-Type: text/plain; charset="windows-1252"; format="flowed" Content-Transfer-Encoding: quoted-printable Subject: Re: [diamon-discuss] My experience on perf, CTF and TraceCompass, and some suggection. List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wang Nan Cc: Xinwei Hu , "diamon-discuss@lists.linuxfoundation.org" , lttng-dev@lists.lttng.org, =?windows-1252?Q?Genevi=E8ve_Bastien?= , tracecompass developer discussions On 2015-02-09 11:55 PM, Wang Nan wrote: > On 2015/2/10 4:13, Alexandre Montplaisir wrote: >> [...] >> >> So in this example we could see right away that the average duration is = around 10-15 ms, but we have some outliers that took more than 20 ms, so it= would be interesting to zoom in there to get more details. And eventually = clicking on one particular occurrence could bring you to the exact point in= the trace where it happened (or create bookmarks for the outlier entries, = etc.) >> > Looks good. It should be better if users are able to define their own mat= ching rules. Absolutely! We can have pre-defined rules for the known domain (system=20 calls, IRQs, and so on), but then it'd be easy to let the user enter an=20 event name for the "start" and an event name for the "end". I was also thinking, we could even use general filters to define what is=20 a start and an end event. It would require some refactoring due to the=20 way filters are organized at the moment, so it wouldn't be trivial, but=20 eventually we may want to get there. I'm currently working on the side on a prototype of the "event matching"=20 table view, I will let you know once I have an initial version working,=20 so we can see if/how useful it is. > > In addition, do you think about chaining more than 2 events together? Som= e procedures, such as IO and network, can be traced at different layers, an= d we are able to chain events caused by same sources together with some cul= es. Please refer to: > > http://comments.gmane.org/gmane.linux.kernel/1883569 > > Which we are working on. > Genevi=E8ve (added in CC) is currently working on virtual machine=20 analyses, where we can match events from a kernel trace on a host to a=20 kernel trace in a guest, and so on. The "layering" and general matching=20 of events should be similar. Maybe she has some ideas if the event=20 matching part could be reused somehow? Cheers, Alexandre