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

Exposing the node capacity via chitchat #4083

Merged
merged 3 commits into from
Nov 9, 2023

Conversation

fulmicoton
Copy link
Contributor

No description provided.

@fulmicoton fulmicoton force-pushed the issue/4082-capacity-in-node-config branch 5 times, most recently from b58eee0 to dacaa38 Compare November 6, 2023 04:33
@fulmicoton fulmicoton force-pushed the issue/4082-capacity-in-node-config branch 2 times, most recently from 9eff4dc to f3e5b7e Compare November 8, 2023 03:27
@fulmicoton fulmicoton force-pushed the issue/4082-capacity-in-node-config branch 3 times, most recently from 881aac0 to 2ee9fca Compare November 8, 2023 05:56
Copy link
Member

@guilload guilload left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: CpuCapacity is also sometimes used for measuring a load or a threshold. It might be better to use CpuUnits for the type, and let the variable names tell us whether it's a capacity, load, etc.

This new CpuCapacity type is used to both expressed
the available capacity in indexer nodes, and
the load associated on shards.

As a result, the quantity we use for the latter
is semantically shifted from the CPU spent on the
indexer actor, to the estimated CPU cost of an
entire pipeline. (x4)
@fulmicoton fulmicoton force-pushed the issue/4082-capacity-in-node-config branch from 870904f to aa540f9 Compare November 9, 2023 02:33
@fulmicoton fulmicoton enabled auto-merge (squash) November 9, 2023 02:33
@fulmicoton fulmicoton force-pushed the issue/4082-capacity-in-node-config branch from aa540f9 to 7185fb1 Compare November 9, 2023 03:25
@fulmicoton fulmicoton merged commit 2613aee into main Nov 9, 2023
4 checks passed
@fulmicoton fulmicoton deleted the issue/4082-capacity-in-node-config branch November 9, 2023 03:48
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

Successfully merging this pull request may close these issues.

2 participants