CallTree exposes a lot of performance information, sometimes, it is too much. We introduced a call tree filter to reduce the noise.
With the ability to filter out stacks on the call tree, it will be easier to focus onto modules that are interesting.
Click the ⭙ sign right to the module name to hide the specific module. This is an easy way to hide events for modules that are out of scope.
Tips: notice the !
sign at the end of the module name.
Try the Suggested
button. It will add the filters to hide most of the framework events from the call tree.
Click 'Hide More' first to bring up the text box. In the text box, typing in the strings for filter and press Enter or use the Hide
button to hide them.
Tips: Try to hide more than one string separate by semicolon like Microsoft;System
.
Bring back hidden events
To remove a string from the list of hidden events, use the ╳ button to the right of the strings in the list.
- It hides the stack that matches;
- It is case sensitive;
- It is partial string match;
Despite the characteristics of the filters, you might notice it not working as expected. There are several caveats that might become interesting.
It might filter out ancestors for the interested node. Expand the tree so that the information is loaded before applying a filter on it.
Under the hood, the filter matches the raw label rather than the polished display text. For example, CPU_TIME
is displayed as CPU Time
, but the filter will still only match CPU_TIME
.
To find out the raw label, hover the mouse over the text:
We are looking into providing better suggestion of filters as well as better ways to add/remove filters. Please feel free to open issues on the GitHub if there's suggestions for the filters.