feat: register profile command #3560
Merged
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.
Motivation
Closes #2273
Requires this Vernier PR to ship and a new version to be released. ✅
This adds a way to profile the currently open file using Vernier, and display the output in editor (VSCode will also display numbers inline with the file).
Implementation
Registers a command that uses Vernier under the hood with the active file and open the
.cpuprofile
file.Automated Tests
Since this was a straightforward command and I didn't see tests for similar commands, I opted to not add a test here. Happy to extract this to a function and test it if we'd prefer to do so.
Manual Tests
Profile current file
command (either from the palette or editor menu of active file).cpuprofile
open. When you click back to the profiled file, VSCode should automatically annotate lines with perf information.ProfileCurrentFileDemo.mov