You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
Currently timing results are automatically related to any active parent timings. This makes sense if (and only if) all these timings are actually related. However in modern multi-threaded applications it is not always the case that two timings are related.
An example is when performing initialization of one part of the application while also starting the UI. In this case the user could be performing UI actions while the initialization is still running, thereby linking the timing results of the initialization and the UI.
So it would be sensible if we could group timing results by area or something similar.
The text was updated successfully, but these errors were encountered:
Currently timing results are automatically related to any active parent timings. This makes sense if (and only if) all these timings are actually related. However in modern multi-threaded applications it is not always the case that two timings are related.
An example is when performing initialization of one part of the application while also starting the UI. In this case the user could be performing UI actions while the initialization is still running, thereby linking the timing results of the initialization and the UI.
So it would be sensible if we could group timing results by area or something similar.
The text was updated successfully, but these errors were encountered: