CrunchyData / postgres-operator

Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
https://access.crunchydata.com/documentation/postgres-operator/v5/
Apache License 2.0
3.94k stars 593 forks source link

How to limit or prevent the impact #3889

Closed clyang82 closed 6 months ago

clyang82 commented 7 months ago

Questions

My case is that I have five components to share the same postgres (installed by crunchy operator). I may choose single DB with separate schema or separate DB. From my experience, one component is using too many resources. How could we prevent or limit the impact from affecting performance for others? Thanks for your advice.

Environment

Please provide the following details:

ValClarkson commented 6 months ago

Hi @clyang82, Thanks for submitting this issue but this question may be more suited to our PGO project community discord, that being said have you considered 5 postgres clusters instead of a shared postgres cluster?

clyang82 commented 6 months ago

Thanks @ValClarkson for introducing the discord. Yes. for sure we can have 5 postgres clusters. but considering the expense, I am looking for if postgres cluster can be shared.

ValClarkson commented 6 months ago

HI @clyang82 I see you reached out in discord, closing this issue