Differences of profiles (with sankey)

Baseline (base)

[+] [-] Profile Specification [-] [+]
origin	072594f42c86c2412c01a82acb4d69fc81795dfe
command	./stress-ng --mmap 1 --verbose --oomable --metrics-brief -t 23 --yaml kernel1_threads_001_iterations_01_run_002_mmap_001.yaml
collector command	ktrace --with-sudo=True --output-profile-type=flat --bpfring-size=167772160 --use-multiprobes=True --cmd-names=['stress-ng', 'stress-ng-mmap'] --repeat-perf=5 --probe-type=kprobe --precollect-symbols-by=['kperf', 'perf']
kernel	kernel1
boot info	BOOT_IMAGE=(hd0,msdos1)/vmlinuz-kernel1 root=/dev/mapper/rhel_zaba-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_zaba-swap rd.lvm.lv=rhel_zaba/root rd.lvm.lv=rhel_zaba/swap console=ttyS0,115200 mitigations=on
host	server1
cpu (total)	48
memory (total)	125.3 GiB

Target (tgt)

[+] [-] Profile Specification [-] [+]
origin	072594f42c86c2412c01a82acb4d69fc81795dfe
command	./stress-ng --mmap 1 --verbose --oomable --metrics-brief -t 23 --yaml kernel1_threads_001_iterations_01_run_002_mmap_001.yaml
collector command	ktrace --with-sudo=True --output-profile-type=flat --bpfring-size=167772160 --use-multiprobes=True --cmd-names=['stress-ng', 'stress-ng-mmap'] --repeat-perf=5 --probe-type=kprobe --precollect-symbols-by=['kperf', 'perf']
kernel	kernel2
boot info	BOOT_IMAGE=(hd0,msdos1)/vmlinuz-kernel2 root=/dev/mapper/rhel_zaba-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_zaba-swap rd.lvm.lv=rhel_zaba/root rd.lvm.lv=rhel_zaba/swap console=ttyS0,115200 mitigations=on
host	server1
cpu (total)	48
memory (total)	125.3 GiB

[+] [-] Help / Tips [-] [+]
Tip 1	Click on a row to explore the results in a form of Sankey Graph (below the table).
Tip 2	Click on [+] to open a detailed report about concrete calling contexts.
Tip 3	Filter the results through select form on the bottom of table (for selected columns).

	Unit	Change	Metric	Absolute Difference	Relative Difference

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Search:

[+] [-] Help / Tips [-] [+]
Tip 1	Look for the topmost widest rectangle.
Tip 2	Click on the node to explore the results in a form of Sankey Graph (below the table).
Tip 3	Colours are picked randomly (but uniformly); they don't signal any scale.
Tip 4	The bigger the rectangle the more often the UID was seen on the stack.
Tip 5	The higher the flame the more nested calls were made in the context.

Threshold:	Min: Max:
Show:	Baseline	Target	Incr (vs base)	Equal	Decr (vs base)
Metric:

[+] [-] Help / Tips [-] [+]
Tip 1	Use the tools at top-right corner of the graph to expand/fold the callers/callees.
Tip 2	Wide red edges are (generally) bad; wide green edges are (generally) good.