Update info on plugins (#5101)

Also add a bit more info on memory usage, due to #5098

1 files changed, 6 insertions, 17 deletions

diff --git a/docs/Performance.md b/docs/Performance.md
index 629fcbf699..b08549f116 100644
--- a/docs/Performance.md
+++ b/docs/Performance.md
@@ -110,6 +110,7 @@ Edit `/etc/netdata/netdata.conf`, find the `[plugins]` section:
 	apps = no
 	charts.d = no
 	node.d = no
+	python.d = no
 
 	plugins directory = /usr/libexec/netdata/plugins.d
 	enable running new plugins = no
@@ -128,6 +129,7 @@ plugin|description
 `apps`|a plugin that monitors system processes. It is very complex and heavy (consumes twice the CPU resources of the netdata daemon), so if you don't need to monitor the process tree, you can disable it.
 `charts.d`|BASH plugins (squid, nginx, mysql, etc). This is a heavy plugin, that consumes twice the CPU resources of the netdata daemon.
 `node.d`|node.js plugin, currently used for SNMP data collection and monitoring named (the name server).
+`python.d`|has many modules and can use over 20MB of memory.  
 
 For most IoT devices, you can disable all plugins except `proc`. For `proc` there is another section that controls which functions of it you need. Check the next section.
 
@@ -135,30 +137,17 @@ For most IoT devices, you can disable all plugins except `proc`. For `proc` ther
 
 ### 2. Disable internal plugins
 
-In this section you can select which modules of the `proc` plugin you need. All these are run in a single thread, one after another. Still, each one needs some RAM and consumes some CPU cycles.
+In this section you can select which modules of the `proc` plugin you need. All these are run in a single thread, one after another. Still, each one needs some RAM and consumes some CPU cycles. With all the modules enabled, the `proc` plugin adds ~9 MiB on top of the 5 MiB required by the netdata daemon. 
 
 ```
 [plugin:proc]
 	# /proc/net/dev = yes                       # network interfaces
 	# /proc/diskstats = yes                     # disks
-	# /proc/net/snmp = yes                      # generic IPv4
-	# /proc/net/snmp6 = yes                     # generic IPv6
-	# /proc/net/netstat = yes                   # TCP and UDP
-	# /proc/net/stat/conntrack = yes            # firewall
-	# /proc/net/ip_vs/stats = yes               # IP load balancer
-	# /proc/net/stat/synproxy = yes             # Anti-DDoS
-	# /proc/stat = yes                          # CPU, context switches
-	# /proc/meminfo = yes                       # Memory
-	# /proc/vmstat = yes                        # Memory operations
-	# /proc/net/rpc/nfsd = yes                  # NFS Server
-	# /proc/sys/kernel/random/entropy_avail = yes # Cryptography
-	# /proc/interrupts = yes                    # Interrupts
-	# /proc/softirqs = yes                      # SoftIRQs
-	# /proc/loadavg = yes                       # Load Average
-	# /sys/kernel/mm/ksm = yes                  # Memory deduper
-	# netdata server resources = yes            # netdata charts
+...
 ```
 
+Refer to the [proc.plugins documentation](../collectors/proc.plugin/) for the list and description of all the proc plugin modules.
+
 ### 3. Lower internal plugin update frequency
 
 If netdata is still using a lot of CPU, lower its update frequency. Going from per second updates, to once every 2 seconds updates, will cut the CPU resources of all netdata programs **in half**, and you will still have very frequent updates.