-
Notifications
You must be signed in to change notification settings - Fork 193
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 doc about profiling Alloy #1781
Conversation
c875e13
to
e557822
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First pass at an edit :-)
Co-authored-by: Clayton Cornell <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor tweak and we can get this one published
@ptodev Do we want to backport this? I am guessing yes? |
Co-authored-by: Clayton Cornell <[email protected]>
Sure, why not :) I added a backport label for all the previous releases. Thank you for the review! |
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit c3b9f51)
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit c3b9f51)
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit c3b9f51)
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit c3b9f51)
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> (cherry picked from commit c3b9f51)
* Add doc about profiling Alloy * Apply suggestions from code review Co-authored-by: Clayton Cornell <[email protected]> * Update docs/sources/troubleshoot/profile.md Co-authored-by: Clayton Cornell <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]>
We often get asked to help with Alloy consumiing lots of memory. It would be helpful to point people to a doc.
If there is a bug in Alloy that's causing the high consumption, then the doc would help people gather enough information to submit a GitHub issue. Even if there is no bug in Alloy, this doc could still help some users to gain more insight into what is consuming memory/CPU.