Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to limit or prevent the impact #3889

Open
clyang82 opened this issue Apr 15, 2024 · 2 comments
Open

How to limit or prevent the impact #3889

clyang82 opened this issue Apr 15, 2024 · 2 comments
Labels

Comments

@clyang82
Copy link

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:

  • Platform: (OpenShift)
  • Platform Version: (e.g. 1.20.3, 4.7.0)
  • PGO Image Tag: (e.g. ubi8-5.x.y-0)
  • Postgres Version (e.g. 15)
  • Storage: (e.g. hostpath, nfs, or the name of your storage class)
@ValClarkson
Copy link
Contributor

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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants