GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||
GeezerVison is showing github.com — Add tools for PowerShell perf analysis by lzybkr · Pull Request #7595 · PowerShell/PowerShell Conversation
|
|
I'm so happy!! Maybe add some info regarding using builds with symbols (cross gened) to get usable stacks? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
That's... 1 GB of buffers? Seems a bit excessive.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Indeed. I forget where I copied that profile from and it looks like it's not actually being used so I'll just delete the file.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Without a System collector this profile won't be usable by itself (it won't have process, thread, or loader events) - the user will always have to start at least one other session alongside this in order to make sense of the data in WPA.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Yep, I'm removing this profile.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
These wprp files aren't WPA regions files, they are WPR profiles.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Yep, I clearly wasn't thinking when I wrote that - I'm removing the files.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Your other profiles capture a small subset of the events this one does, but use a much larger set of buffers.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This is the profile we care about. I don't recall seeing dropped events, so maybe this is fine?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Despite what the outdated MSDN documentation says, the Name attribute has been optional since Windows 8.1, and should be considered deprecated.
There's probably no value targeting the WPR that ships with the Windows 8 ADK as opposed to the Windows 8.1 ADK. Newer versions of the ADK can be installed on older OS releases.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I appreciate the review. I agree, folks profiling PowerShell probably aren't running Win8 so I'll just remove the Name attribute.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should this be uncommented?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
No, it's expensive and not normally needed, but good to know about so I left it. I'll add a comment to explain.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can we make this a parameter? So we can launch a different pwsh.exe version than the one we are using.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Sure.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Please add EOL
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment why sometimes the module name has .ni while sometimes it doesn't
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Uh, I'm not sure, and maybe not relevant to PowerShell Core. This file isn't really that refined at all, so the hope is folks will contribute and make it more useful,
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I remember now, comment added.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Please add EOL
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry about amending instead of adding, mostly just renaming and reformatting, but all feedback should be addressed now. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Can't hold breath much longer... |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
FYI. 18 spelling errors in tools/performance/README.md are causing Travis CI build failure. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I see 0 spelling errors and have no plans to make the tool happy, so a maintainer can fix or else close the PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The tool fails on stuff like |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Staffan Gustafsson (@powercode) - yes, I reviewed what it complained about, it also complained about But my point - we have humans reviewing and didn't complain. The tool should not block PRs. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Updated the spellings file. Once CI is complete, I will merge. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Jason Shirk (@lzybkr) Thanks for your contribution!! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.