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

[core] Split giant ray core C++ targets into small ones(GCS server) #50602

Open
400Ping opened this issue Feb 14, 2025 · 1 comment
Open

[core] Split giant ray core C++ targets into small ones(GCS server) #50602

400Ping opened this issue Feb 14, 2025 · 1 comment
Assignees
@400Ping
Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability

Comments

@400Ping
Copy link
Contributor

400Ping commented Feb 14, 2025

As of now, ray core uses bazel as build system, which encourages small targets.
Ray core is not following the best practice, which bundles all related files into several giant targets. For more information, check out the master issue

Part of #50586
@400Ping 400Ping mentioned this issue Feb 14, 2025
Open
11 tasks
@dentiny dentiny added enhancement Request for new feature and/or capability core Issues that should be addressed in Ray Core labels Feb 14, 2025
@dentiny
Copy link
Contributor

dentiny commented Feb 14, 2025

Thank you for your help! Appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@400Ping 400Ping

Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dentiny @400Ping