-
Notifications
You must be signed in to change notification settings - Fork 632
Description
Is there an existing issue already for this feature request/idea?
- I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.
What problem is this feature going to solve? Why should it be added?
Currently we don't know the amount of resources consumed by the instance manager inside every PostgreSQL pod, which let us without knowledge if it's behaving properly or not
Describe the solution you'd like
Add the possibility to start the pprof server inside every instance to report the proper information to the pyroscope/grafana to gather the data and generate the proper graphs.
This needs to be disabled or enabled independently to the pprof server running on the operator itself since it may not be desired to have both running at the same time.
The proposal is to add this as another parameter passed to the pods at starting point, for every process including: bootstrap, run, join, etc. the meaning it's to facilitate the gather of data on every process.
Doing this profiling could help to improve the memory and cpu usage as well as the resources used by the goroutines.
Describe alternatives you've considered
There's no alternative solution to do a proper profiling that can be consistently used in the future
Additional context
No response
Backport?
Yes
Are you willing to actively contribute to this feature?
Yes
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Type
Projects
Status