WIP: Update Cody performance tracing documentation #1047
Conversation
This file contains hidden or 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
* Split performance tracing instructions into separate VS Code and JetBrains sections * Improve VS Code tracing instructions with clearer step-by-step format * Add new section for JetBrains/IntelliJ performance tracing * Update instructions to focus on memory profiling rather than just performance tracing * Add detailed steps for saving and sharing profile files Test plan: - Verified instructions for VS Code on macOS - Verified instructions for JetBrains IDEs on macOS - Manually tested the chrome://inspect workflow on both platforms
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
enriquegh
changed the title
|
Hi @enriquegh is this PR ready? I see a WIP in the title. |
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.
Test plan:
Pull Request approval
You will need to get your PR approved by at least one member of the Sourcegraph team. For reviews of docs formatting, styles, and component usage, please tag the docs team via the #docs Slack channel.