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

release-21.2: flowinfra: make max_running_flows default depend on the number of CPUs #12836

Closed
cockroach-teamcity opened this issue Jan 25, 2022 · 0 comments
Closed

release-21.2: flowinfra: make max_running_flows default depend on the number of CPUs #12836

cockroach-teamcity opened this issue Jan 25, 2022 · 0 comments
Assignees
@mdlinville
Labels
C-product-change release-21.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jan 25, 2022 •
edited by exalate-issue-sync bot
Loading

Exalate commented:

cockroachdb/cockroach#75509 --- Release note (ops change): The meaning of sql.distsql.max_running_flows cluster setting has been extended so that when the value is negative, it would be multiplied by the number of CPUs on the node to get the maximum number of concurrent remote flows on the node. The default value is -128, meaning that on a 4 CPU machine we will have up to 512 concurrent remote DistSQL flows, but on a 8 CPU machine up to 1024. The previous default was 500.

Jira Issue: DOC-2414
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mdlinville mdlinville

Labels
C-product-change release-21.2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mdlinville @taroface @cockroach-teamcity