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

Add doc page with sizing guide for common platform #2349

Open
Tracked by #2351
ylebi opened this issue Jan 21, 2025 · 0 comments
Open
Tracked by #2351

Add doc page with sizing guide for common platform #2349

ylebi opened this issue Jan 21, 2025 · 0 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ylebi
Copy link
Collaborator

ylebi commented Jan 21, 2025

We should have a simple page that shows how to size a ScyllaCluster for the most common machine types, like i4is. when you want to fit the whole machine, like

  • max storage used
  • cpu limits
  • memory request

And a simple explanation on how to discover such values on other machine types not listed there.

Ref: #2190

@ylebi ylebi added kind/documentation Categorizes issue or PR as related to documentation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 21, 2025
@mflendrich mflendrich added the lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants