[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tracecompass-dev] Performance of CPU usage analyses with many threads involved
- From: Genevieve Bastien <gbastien+lttng@xxxxxxxxxxxx>
- Date: Mon, 18 Feb 2019 10:44:53 -0500
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
Wow, reading this bug report brings back memories... Claudette nodes...
Anyway, indeed, on the backend side, there should be no performance problems anymore, and from doing a bit of sampling after reading your mail, the performance problem you're experience comes from the frontend: The UI spends most of its time rendering checkboxes of the tree items... Because there's a lot of items in this tree, yet only a few of them are visible. I think the 'tree' widget of those views should be more lazy and display only the visible items instead of all of them. There should be a bug for that. Especially that we have more and more of that type of views with a lot of items...
Thanks for bringing this up,
On 2019-02-18 8:05 a.m., rreinsberger@xxxxxxxxx wrote:
> Evaluating the CPU usage analyses and view I used sample/test data from here:
> â and from here (see file attachment in the report):
> Trying to update the CPU usage graph with all threads selected the analyses took a very long time (>30 min) until Trace Compass (v4.2) was eventually rendered unresponsive.
> It seems that in the bug report referred to above this problem (or at least parts of it) were addressed. However, I am not sure what performance and results are to be expected for this test traces. Is the CPU usage supposed to work and produce results with this trace data in TC version 4.2?
> tracecompass-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit