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] Actor/Task Memory resource allocation should be separate from Object Store allocation #49344

Open
alexeykudinkin opened this issue Dec 18, 2024 · 1 comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P1 Issue that should be fixed within a few weeks

Comments

@alexeykudinkin
Copy link
Contributor

What happened + What you expected to happen

Currently, when scheduling Actors or Tasks with memory resource specified i'm expecting that they will be allocated based on memory available on the node for use as private process heap.

This is problematic in the following scenario in Ray Data:

  1. I'm configuring region of node memory to be dedicated for the Object Store (say 35%)
  2. Remainder of the memory i want to be split b/w Tasks/Actors based on their corresponding memory allocation.

Instead i observed that we schedule based on the total available memory that also includes the Object Store.

Versions / Dependencies

2.41

Reproduction script

See above

Issue Severity

Medium: It is a significant difficulty but I can work around it.

@alexeykudinkin alexeykudinkin added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) core Issues that should be addressed in Ray Core labels Dec 18, 2024
@alexeykudinkin
Copy link
Contributor Author

Here's an example of this kind of allocation where 2 actors that aren't supposed to fit on the same node are scheduled onto one:

image

@ruisearch42 ruisearch42 added P1 Issue that should be fixed within a few weeks and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P1 Issue that should be fixed within a few weeks
Projects
None yet
Development

No branches or pull requests

2 participants