Julien Desfossez
Julien Desfossez
Hi, I am new to Faust and I am trying to understand how to make sure I have processed the oldest event by partition. I am using the group_by syntax...
The histograms are relative to the values, but when printing percentages we should scale to 100% Per-TID Usage Process Migrations Priorities ###### ████████████████████████████████████████████████████████████████████████████████ 0.07 % rcu_sched (7) 0 [20] █████████████████████████████████████████████████...
Make sure the event and field names specified in the --period argument do exist in the metadata of the trace(s). This will save time instead of waiting for the analysis...
``` $ ~/projects/src/lttng/lttng-analyses/lttng-iousagetop --skip-validation --tid 2873 --debug lttng-startup-1551/ Traceback (most recent call last): File "/ssd/milian/projects/src/lttng/lttng-analyses/lttnganalyses/cli/command.py", line 73, in _run_step fn() File "/ssd/milian/projects/src/lttng/lttng-analyses/lttnganalyses/cli/command.py", line 341, in _run_analysis self._automaton.process_event(event) File "/ssd/milian/projects/src/lttng/lttng-analyses/lttnganalyses/linuxautomaton/automaton.py", line...
Just compute the total time spent in each syscall type
If those are enabled, use them. That would allow users to record traces without needing to enable sched_switch events which can be high throughput.
The method we currently use to identify the vpcu threads in qemu only works with libvirt's approach. Using QMP will be more generic: ``` query-cpus-fast ```