zalando / zalando/postgres-operator
PSQL Instances high ram usage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
PSQL instances use about 600 MB of RAM in idle mode, while a normal PSQL POD uses about 60 MB of RAM. What is the cause of this exabrute resource usage and management?
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
- **Where do you run it - cloud or metal? Kubernetes (Metakube)
- Are you running Postgres Operator in production? yes
- Type of issue? Question maybe Bug report
Some general remarks when posting a bug report:
Logs look fine, we don't have any issues with the PSQL Instances BUT the Instances are using to much resources (RAM). We are using WALG to S3. The RAM Usage (high usage) is constantly on idle Instances in active instances, the usage ist increasing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified. Start by reproducing and measuring memory growth in idle PostgreSQL instances on Kubernetes, comparing them with a normal PostgreSQL pod and checking the WAL-G to S3 setup. Done means identifying the cause of the excess RAM usage and documenting or validating an appropriate management path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100