-
Notifications
You must be signed in to change notification settings - Fork 182
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
base: main
Are you sure you want to change the base?
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 <131809008+clayton-cornell@users.noreply.github.com>
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
You may not want to upload your profiles to a public location. | ||
{{< /admonition >}} | ||
|
||
The port you use to send the HTTP request is governed by Alloy's `--server.http.listen-addr` [command line argument][cmd-cli]. |
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.
The port you use to send the HTTP request is governed by Alloy's `--server.http.listen-addr` [command line argument][cmd-cli]. | |
The port you use to send the HTTP request is controlled by the `--server.http.listen-addr` [command line argument][cmd-cli]. |
Missed this one in the first pass. I think we can drop the Alloy's
and assume the reader knows we are talking about the CLI arg in Alloy here.
@ptodev Do we want to backport this? I am guessing yes? |
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.