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

[Feature] Performance problems when the cluster is running on a small hashrate #4

Open
renajin opened this issue Aug 5, 2021 · 1 comment

Comments

@renajin
Copy link
Contributor

renajin commented Aug 5, 2021

Feature Request

Is your feature request related to a problem? Please describe:
If a transaction peak come, how to scale-out immediately without affecting current sql process, or can we have any other method to handle this emergencies?

Describe the feature you'd like:

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@renajin
Copy link
Contributor Author

renajin commented Aug 9, 2021

When initially creating small size cluster, we set cpu limit to 1/4 of the maximum hashrate, so this cluster can withstand a certain amount of transaction peak.

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

No branches or pull requests

1 participant