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.

Sign up for GitHub

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

Jump to bottom

sizing guidance document #7818

Open
taroface opened this issue Jul 29, 2020 · 2 comments
Open

sizing guidance document #7818

taroface opened this issue Jul 29, 2020 · 2 comments
Assignees
@taroface
Labels
no-issue-activity P-1 High priority; must be done this release

Comments

@taroface
Copy link
Contributor

taroface commented Jul 29, 2020 •
edited by exalate-issue-sync bot
Loading

Ryan Kuo (taroface) commented:

Our Production Checklist mentions provisioning resources "for your workload" but doesn't provide further guidance on this.

A separate article on "sizing" a deployment for your applications needs is necessary. It should cover sizing:

  • For workload
  • For storage
  • Antipatterns

Should include guidance on how to run load-test simulations, which help determine how to configure parameters such as the interval between SIGTERM and SIGKILL during node shutdown (relates to #6951).

@BramGruneir's interactive survivability app would also be appropriate to include here.

References:

Jira Issue: DOC-599
@taroface taroface added P-1 High priority; must be done this release A-deploy-ops labels Jul 29, 2020
@taroface taroface self-assigned this Jul 29, 2020
@taroface taroface changed the title create sizing guidance document sizing guidance document Jul 29, 2020
@taroface taroface mentioned this issue Sep 22, 2020
Open
@taroface taroface mentioned this issue Oct 6, 2020
Closed
@taroface taroface mentioned this issue Dec 10, 2020
Closed
@github-actions
Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB docs!

@BramGruneir
Copy link
Member

This would still be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taroface taroface

Labels
no-issue-activity P-1 High priority; must be done this release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BramGruneir @taroface @jseldess