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

Add EtlToSpeedScope UserCommand #1690

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

EmosewaMC
Copy link
Contributor

Resolves #1688

Adds a UserCommand to convert etl files to .speedscope.json for data parsing. Added some parameters to filter the data down as well that are also used for other commands like process to filter on and warm symbol lookups.

@EmosewaMC
Copy link
Contributor Author

its been a couple of months since this was looked at - just wanted to throw a quick bump here

Copy link
Member

@brianrob brianrob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pinging this. A couple of comments below.

{
throw new ApplicationException("Invalid number to lookup with.");
}
etlFile.CPUStacks().LookupWarmSymbols(warmSymbolLookupThreshold);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The call to CPUStacks() creates a new instance of Stacks unconditionally, meaning that the last line of this method will override this line if the caller specifies a process filter. You will want to save the StackSource in a local variable and then use it to generate the file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correcting myself - the filter does stick. However, the stacks get calculated twice.

}
etlFile.CPUStacks().LookupWarmSymbols(warmSymbolLookupThreshold);
}
SpeedScopeStackSourceWriter.WriteStackViewAsJson(etlFile.CPUStacks().StackSource, outputName);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lookupWarmSymbolsMinimumValue only has an impact if a process filter is specified. Presumably this should be used unconditionally?

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

Successfully merging this pull request may close these issues.

Adding a UserCommand to convert etl files to speedscope.json or updating NetperfToSpeedScope
2 participants