-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Conversation
Signed-off-by: Ruiyang Wang <rywang014@gmail.com>
e868a4f
to
f8dec04
Compare
Could you elaborate how to remove it all? |
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. |
There was a problem hiding this 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
Signed-off-by: Ruiyang Wang <56065503+rynewang@users.noreply.github.com>
) 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>
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.