mudhorn/prometheus
1
0
Fork 0
mirror of https://github.com/prometheus/prometheus.git synced 2025-03-05 20:59:13 -08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

docs: remove obsolete info in getting started

Browse source 
Go automatically configures the number of used threads appropriately
and tweaking it is no longer relevant for a basic setup of Prometheus.
The baseline consumption tied to the storage layer no longer applies.
This commit is contained in:
Fabian Reinartz 2017-10-28 12:09:03 +02:00
parent 8a2b5a3936
commit 8cc78b36a2
1 changed files with 0 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/getting_started.md
View file

@ -77,17 +77,6 @@ You can also verify that Prometheus is serving metrics about itself by
navigating to its metrics endpoint: navigating to its metrics endpoint:
[localhost:9090/metrics](http://localhost:9090/metrics) [localhost:9090/metrics](http://localhost:9090/metrics)
The number of OS threads executed by Prometheus is controlled by the
`GOMAXPROCS` environment variable. As of Go 1.5 the default value is
the number of cores available.
Blindly setting `GOMAXPROCS` to a high value can be counterproductive. See the
relevant [Go FAQs](http://golang.org/doc/faq#Why_no_multi_CPU).
Prometheus by default uses around 3GB in memory. If you have a
smaller machine, you can tune Prometheus to use less memory. For details,
see the [memory usage documentation](storage.md#memory-usage).
## Using the expression browser ## Using the expression browser
Let us try looking at some data that Prometheus has collected about itself. To Let us try looking at some data that Prometheus has collected about itself. To