Skip to content
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.

Nuclei.Diagnostics: Allow grouping of timing results #2

Closed
pvandervelde opened this issue Dec 3, 2013 · 1 comment
Closed

Nuclei.Diagnostics: Allow grouping of timing results #2

pvandervelde opened this issue Dec 3, 2013 · 1 comment
Assignees
@pvandervelde
Labels
enhancement

Comments

@pvandervelde
Copy link
Member

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.
@ghost ghost assigned pvandervelde Dec 3, 2013
pvandervelde added a commit that referenced this issue Dec 4, 2013
@pvandervelde
Adding the TimingGroup class which is used to identify to which group…
f2c9e5d 
… a specific timing belongs. This allows separating timings based on their logical area or grouping.

references issue #2
pvandervelde added a commit that referenced this issue Dec 4, 2013
@pvandervelde
Adding the timing group for the communication system.
5176cbf 
references issue #2
@pvandervelde
Copy link
Member Author

Fixed in version 0.7.0.0

@pvandervelde pvandervelde mentioned this issue Apr 6, 2014
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pvandervelde pvandervelde

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pvandervelde