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

[Plasma] Support setting memory quotas per plasma client for better isolation #22364

Closed
asfimport opened this issue Jul 16, 2019 · 1 comment
Closed

Comments

@asfimport
Copy link

Currently, plasma evicts objects according a global LRU queue. In Ray, this often causes memory-intensive workloads to fail unpredictably, since a client that creates objects at a high rate can evict objects created by clients at lower rates. This is despite the fact that the true working set of both clients may be quite small.

cc @pcmoritz

Reporter: Eric Liang / @ericl
Assignee: Eric Liang / @ericl

PRs and other links:

Note: This issue was originally created as ARROW-5955. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Philipp Moritz / @pcmoritz:
Issue resolved by pull request 4885
#4885

@asfimport asfimport added this to the 0.15.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant