Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically create a textual trace summary #140

Open
randomascii opened this issue Jan 16, 2020 · 0 comments
Open

Automatically create a textual trace summary #140

randomascii opened this issue Jan 16, 2020 · 0 comments

Comments

@randomascii
Copy link
Collaborator

IdentifyChromeProcesses.py is a useful summary of an ETW trace, if you are a Chrome developer primarily interested in the mapping of process IDs to Chrome process types. However there is so much more than could be done, especially now that the Trace Processing library is available:

https://randomascii.wordpress.com/2020/01/05/bulk-etw-trace-analysis-in-c/

Obvious snippets that could be in a summary include:

  • Options used when recording the trace
  • The length (in time) of the trace
  • Whether there are any lost events or time inversions
  • Average CPU utilization (need to excluded rundown), and old sections of circular-buffer tracing, top CPU consumers, average disk utilization, active window/windows, whether CPU throttling was detected, QPC frequency, ???
  • What type of trace it is ("normal", heap tracing, heap snapshot)
  • If a heap tracing or heap snapshot trace then things like how many allocations, etc.

Ideally this summary would be in a delimited block so that the summary could be regenerated when new features are added, replacing the old summary. Maybe that would be best done by having it in a separate file, or injected into the trace, and then shown in a tooltip?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant