[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

Hey Genevieve,


thanks for the feedback, here's an image series taken with a xeon phi
trace.

https://imgur.com/a/QRNDMkp


Things to note:


1- even if we cannot read the title, we know that the cpus are
sequential, threads appear when we need them, this makes the resources
view much more vertically scalable.

2- the cfv starts with swappers... they are important, but that means
the first n entries will be taken by them, and they sort of show the
inverse of the cpu usage, this is not super intuitive.


As for the full range, let's make that a new post... I'm all for it btw ;)


Matthew


On 18-05-09 04:31 PM, Geneviève Bastien wrote:
>
> I would agree to put the Resources view forward.
>
>
> 1- The first entries (those seen) of this view are more meaningful
> than the first entries of the Control Flow view that are often some
> swapper or system/sleeping processes.
>
> 2- Resources view has a rather small number of entries compared with
> control flow view, giving a better first glance of the trace.
>
>
> To give a better idea, here are 2 screenshots of those views for full
> zoom for an experiment: Resources [1], Control Flow [2]
>
>
> [1]
> https://secretaire.dorsal.polymtl.ca/~gbastien/screenshots/ResourcesView.png
>
> [2]
> https://secretaire.dorsal.polymtl.ca/~gbastien/screenshots/ControlFlowView.png
>
>
> I would add that opening a trace at full range (until the user
> explicitly selects another range) instead of the first 100ms would
> also be a good idea.
>
>
> Cheers,
>
> Geneviève
>
>
> On 2018-05-09 03:38 PM, Matthew Khouzam wrote:
>>
>> 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.
>>
>>
>> Thoughts?
>>
>>
>> Matthew.
>>
>>
>> [1] https://git.eclipse.org/r/#/c/121958/
>> <https://git.eclipse.org/r/#/c/121958/>
>>
>> Gerrit Code Review <https://git.eclipse.org/r/#/c/121958/>
>> git.eclipse.org
>> Loading Gerrit Code Review... ... Home; Privacy Policy; Terms of Use;
>> Copyright Agent; Legal
>>
>>
>>
>>
>>
>> _______________________________________________
>> tracecompass-dev mailing list
>> tracecompass-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
>
>
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev