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

[core] move GetInternalConfig: NodeInfo -> InternalKV #47755

Merged
merged 6 commits into from
Sep 26, 2024

Conversation

rynewang
Copy link
Contributor

@rynewang rynewang commented Sep 20, 2024

Every time GetInternalConfig reads from table_storage, but it's never mutated. Moves to internal kv as a simple in-mem get (no more read from redis). This itself should slightly update performance. But with #47736 it should improve start up latency a lot in thousand-node clusters. In theory we can remove it all for good, instead just put it as an InternalKV entry. but let's do things step by step.

Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
@rynewang rynewang added the go add ONLY when ready to merge, run all tests label Sep 23, 2024
Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
@jjyao
Copy link
Collaborator

jjyao commented Sep 25, 2024

in theory we can remove it all for good, instead just put it as an internalkv entry. but let's do things step by step

Could you elaborate how to remove it all?

src/ray/gcs/gcs_server/gcs_kv_manager.h Outdated Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_server.cc Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_kv_manager.cc Show resolved Hide resolved
@rynewang
Copy link
Contributor Author

Yeah we can remove InternalConfigTable all for good, instead just use a predefined key to get from internal kv. However as I said that will be a much bigger change (-200 LoC) so I think we can do it in another PR to unblock this important performance gain.

Copy link
Collaborator

@jjyao jjyao left a comment

Choose a reason for hiding this comment

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

We can merge after resolving 2 comments

src/ray/gcs/gcs_server/gcs_kv_manager.cc Outdated Show resolved Hide resolved
src/ray/gcs/gcs_server/gcs_kv_manager.h Outdated Show resolved Hide resolved
Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
@rynewang rynewang enabled auto-merge (squash) September 26, 2024 18:04
src/ray/gcs/gcs_server/gcs_kv_manager.h Outdated Show resolved Hide resolved
Signed-off-by: Ruiyang Wang <56065503+rynewang@users.noreply.github.com>
@rynewang rynewang enabled auto-merge (squash) September 26, 2024 20:35
@rynewang rynewang merged commit 3285452 into ray-project:master Sep 26, 2024
6 checks passed
@rynewang rynewang deleted the config-in-internalkv branch September 26, 2024 23:12
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Oct 15, 2024
)

Every time GetInternalConfig reads from table_storage, but it's never
mutated. Moves to internal kv as a simple in-mem get (no more read from
redis). This itself should slightly update performance. But with ray-project#47736
it should improve start up latency a lot in thousand-node clusters. In
theory we can remove it all for good, instead just put it as an
InternalKV entry. but let's do things step by step.

Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
Signed-off-by: Ruiyang Wang <56065503+rynewang@users.noreply.github.com>
Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants