This repository was archived by the owner on Sep 30, 2024. It is now read-only.
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5477d17 to
8c7c2c8
Compare
d1e6438 to
54f15f5
Compare
8c7c2c8 to
fa9f739
Compare
54f15f5 to
6663fa4
Compare
fa9f739 to
f34c905
Compare
6663fa4 to
8929898
Compare
f34c905 to
7836694
Compare
8929898 to
38163bc
Compare
7836694 to
3e3654d
Compare
38163bc to
3656a7f
Compare
36960b8 to
c69f584
Compare
3656a7f to
5ce6eba
Compare
fd31fb9 to
f7113c0
Compare
5ce6eba to
6c85d79
Compare
f7113c0 to
c5f3b77
Compare
6c85d79 to
2fcddfb
Compare
c5f3b77 to
182220b
Compare
2fcddfb to
0721a1d
Compare
ggilmore
commented
Jun 8, 2024
ggilmore
commented
Jun 8, 2024
Contributor
Author
|
Unforunately, I couldn't see the grafana dashboards for this feature locally since |
eseliger
approved these changes
Jun 10, 2024
Member
eseliger
left a comment
There was a problem hiding this comment.
Let's take it for a spin and see how it performs!
182220b to
5f49f48
Compare
0721a1d to
2d753e5
Compare
5f49f48 to
da9e0db
Compare
2d753e5 to
1b08fce
Compare
da9e0db to
1aea5aa
Compare
aaad947 to
4e3d913
Compare
1aea5aa to
456f90e
Compare
4e3d913 to
0ae625b
Compare
456f90e to
a223c9a
Compare
6f26a2d to
4e75cd4
Compare
a223c9a to
9dd391b
Compare
4e75cd4 to
9fad661
Compare
9fad661 to
4d5defb
Compare
Base automatically changed from
05-20-wip_keep_expriementing_with_linux_memory_observations
to
main
June 10, 2024 21:20
4d5defb to
b7706e7
Compare
Contributor
Author
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.


Closes https://linear.app/sourcegraph/issue/SRC-369/finalize-memory-tracking-in-gitserver-on-linux
This PR adds a memory tracking feature to all gitserver command, using the utilities introduced in https://app.graphite.dev/github/pr/sourcegraph/sourcegraph/62803.
When the GITSERVER_MEMORY_OBSERVATION_ENABLED env var is set, an observer will be spawned that keeps track of the memory usage of the git invocation. This information is available in traces. Additionally, we'll print WARN logs if the commands uses more than 100 MB.
Test plan
Run sg start, and manually tweak the high memory usage threshold down from 500 MB to 1MB.
See log lines similar to the following when I run
sg start(note the memory usage information in the log fields):Note that I have not tested this e2e in a linux system, but I think it's fine to test it on sourcegraph.com since:
Changelog
Adds a new experimental feature to enable track of
gitcommand memory invocations when theGITSERVER_MEMORY_OBSERVATION_ENABLEDenvironment variable is true (off by default).