Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
docs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Administrator
docs
Commits
54f61040
Commit
54f61040
authored
May 04, 2017
by
beorn7
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Operating: Document effects of higher GOGC values
parent
2087d8fa
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
2 deletions
+5
-2
storage.md
content/docs/operating/storage.md
+5
-2
No files found.
content/docs/operating/storage.md
View file @
54f61040
...
...
@@ -40,8 +40,11 @@ memory and thus will perform much worse than it could.
Because Prometheus uses most of its heap for long-lived allocations of memory
chunks, the
[
garbage collection target percentage
](
https://golang.org/pkg/runtime/debug/#SetGCPercent
)
is set to 40 by default. You can still override this setting via the
`GOGC`
environment variable as usual.
is set to 40 by default (rather than the usual 100). You can still override
this setting via the
`GOGC`
environment variable as usual. A higher value
results in fewer memory chunks and less CPU usage, which makes sense in
scenarios where you need to save CPU usage but can afford to have fewer memory
chunks.
For high-performance set-ups, you might need to adjust more flags. Please read
through the sections below for details.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment