Add docs for windows performance analyzer #3149
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #3149 +/- ##
==========================================
- Coverage 50.62% 50.61% -0.01%
==========================================
Files 444 444
Lines 42696 42696
==========================================
- Hits 21613 21612 -1
- Misses 21083 21084 +1 |
nekevss
reviewed
Jul 18, 2023
| Windows have a performance analyzing tool that creates graphs and data tables of Event Tracing for Windows (ETW) events. You can analyze your whole system but also individual binaries too. | ||
| This can be used for performance tracing with Rust programs like Boa. | ||
|
|
||
| For this to work you will need to have your code running in native windows and not WSL. |
There was a problem hiding this comment.
Is WSL ubiquitous enough? Maybe in the interest of clarity it should be fully spelled out.
|
|
||
| Once you've done this navigate to the CPU Usage (Sampled) tab underneath and click the first symbol on the far right, it should be called `Display Graph and Table`. | ||
|
|
||
| Then on the dropdown (same tab) select `Flame By Process, Stack`. If followed correctly you should have something which looks like this: |
There was a problem hiding this comment.
Suggested change
| Then on the dropdown (same tab) select `Flame By Process, Stack`. If followed correctly you should have something which looks like this: | |
| Then on `CPU Usage (Sampled)` View Preset dropdown, located just to the right of the header title, select the `Flame By Process, Stack` option. If followed correctly, you should see something similar to the below: |
|  | ||
|
|
||
| Almost there.. | ||
| Symbols are not showing, WPA doesn't scan symbols by default. You need to click Trace at the top and then `Load Symbols`. |
There was a problem hiding this comment.
Suggested change
| Symbols are not showing, WPA doesn't scan symbols by default. You need to click Trace at the top and then `Load Symbols`. | |
| Symbols are not showing, WPA doesn't scan symbols by default. To load symbols, click Trace in the application menu at the top and then select `Load Symbols`. |
Co-authored-by: Kevin <46825870+nekevss@users.noreply.github.com>
Co-authored-by: Kevin <46825870+nekevss@users.noreply.github.com>
Co-authored-by: Kevin <46825870+nekevss@users.noreply.github.com>
|
We discussed this in our triage and @raskad @nekevss @HalidOdat will try to run it to see if there are any issues on the example. |
raskad
approved these changes
Dec 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds some new documentation for profiling Boa with Windows Performance Analyzer.
This doesn't replace the measureme/crox effort, but offers another way of profiling Boa which may be more suitable to some users.
Please try the guide out and let me know if it makes sense or is missing some steps.
Rendered