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

Feedback: Production Checklist #18618

Open
fqazi opened this issue Jun 3, 2024 · 2 comments
Open

Feedback: Production Checklist #18618

fqazi opened this issue Jun 3, 2024 · 2 comments
Assignees

Comments

@fqazi
Copy link

fqazi commented Jun 3, 2024

Faizan Qazi (fqazi) commented:

Page: https://cockroachlabs.com/docs/v24.1/recommended-production-settings.html

We recently had a question from the community in terms of CRDB being NUMA aware. We should document this is no the case and advice against configurations setup this way, since there is a risk of performance degredation.

What is the reason for your feedback?

[x] Missing the information I need

[ ] Too complicated

[ ] Out of date

[ ] Something is broken

[ ] Other

Additional details

For example: https://stackoverflow.com/questions/78561114/cockroachdb-configuration-on-numa-enabled-processors

Jira Issue: DOC-10413

Copy link

linville (mdlinville) commented:
Jeffrey White Are you still the person who knows most about NUMA? My impression from https://cockroachlabs.atlassian.net/browse/DOC-220 is that NUMA is supported, and that there are best practices we should document (but we didn’t quite get to the bottom of what they were). It seems that Faizan is under the impression that NUMA is not supported.

Copy link

Faizan Qazi (fqazi) commented:
I think we should highlight at a minimum indicate we are not NUMA aware (i.e. CRDB will not automatically tune / allocate resources in a NUMA friendly way). The user themselves will have to use NUMA pinning, etc…

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

2 participants