From 8cc78b36a2812e30c32ef8d889c9d816c8dd2ca1 Mon Sep 17 00:00:00 2001 From: Fabian Reinartz Date: Sat, 28 Oct 2017 12:09:03 +0200 Subject: [PATCH] docs: remove obsolete info in getting started 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. --- docs/getting_started.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/docs/getting_started.md b/docs/getting_started.md index a72684eae..d14d5df58 100644 --- a/docs/getting_started.md +++ b/docs/getting_started.md @@ -77,17 +77,6 @@ You can also verify that Prometheus is serving metrics about itself by navigating to its metrics endpoint: [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 Let us try looking at some data that Prometheus has collected about itself. To