Provide Resource Recommendations / Minimum Requirements

[ghost]

helm-chart/chart/pyroscope/values.yaml

Lines 163 to 174 in b504389

	# -- CPU/Memory resource requests/limits
	resources: {}
	# We usually recommend not to specify default resources and to leave this as a conscious
	# choice for the user. This also increases chances charts run on environments with little
	# resources, such as Minikube. If you do want to specify resources, uncomment the following
	# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
	# limits:
	# cpu: 100m
	# memory: 128Mi
	# requests:
	# cpu: 100m
	# memory: 128Mi

Though I agree that this should be a conscious choice by the user, some enterprise environments do have strict policies on setting resource limits for all deployed services in areas where sensitive processes may be happening.

I noticed in my own use, 100Mi was too small and resulted in the container throwing an OOM error.

Some documentation on minimum memory requirements and CPU recommendations for specific loads should be linked here.

An open question I have is how many services/pods can the collector handle at

limits:
  cpu: 100m
  memory: 128Mi