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
Being apply to filter and group by namespace on the call tree and analysis view would be really useful for analysing which packages have the most time spent in them
For the parser changes ensure we use Memoization to improve performance and avoid over parsing.
The namespace patterns tend to be the same.
All log events should have a namespace associated or be in the default namespace (unmanaged).
If we were to aggregate namespace a parent could have multiple e.g a caller would be in a single namespace but have children from many different ones.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Being apply to filter and group by namespace on the call tree and analysis view would be really useful for analysing which packages have the most time spent in them
For the parser changes ensure we use Memoization to improve performance and avoid over parsing.
The namespace patterns tend to be the same.
All log events should have a namespace associated or be in the default namespace (unmanaged).
If we were to aggregate namespace a parent could have multiple e.g a caller would be in a single namespace but have children from many different ones.
The text was updated successfully, but these errors were encountered: