Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] Promoting the Resources View to first view of Trace Compass LTTng Analysis

Good idea. The CPU cores view can carry a lot of information (which thread and even which function is executing at any given time) and provides an excellent global picture of the state of our system. It may not be too exciting for a simple CPU core machine. On the other extreme, a Xeon Phi with 240 virtual cores will remain a bit overwhelming.

Popular applications such as Top manage the complexity by showing the most active threads on top.

----- Le 9 Mai 18, à 15:38, Matthew Khouzam <matthew.khouzam@xxxxxxxxxxxx> a écrit :

Hey all,

I'd like to discuss moving the resources view to the front of the LTTng perspective.

Historically the Control Flow View was there. Reasons: when we started developing Trace Compass, we had 1 core, maybe 2. Now we have over 16.

Also the resources view has been getting a lot of improvements and I think they should be highlighted.

1- there is a threads entry, so you can see which thread is running on which CPU.

2- The CPU status is now a tree with the contributing IRQ/SoftIRQs under it.

3- The CPU Frequency is a visible entry.

This actually makes two interesting points:

1- the Resources view has most of the data of the control flow view already available in it.

2- It shows data in a more intuitive way when zoomed out

3- It limits the data shown vertically by limiting us to a given resource. (CPU at the moment)

Because of this, and the fact that KernelShark displays data in a similar way already, I propose that we try making the Resources view the star when opening up a Trace Compass kernel trace.



Loading Gerrit Code Review... ... Home; Privacy Policy; Terms of Use; Copyright Agent; Legal

tracecompass-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top