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

Per-client resource allocation? #43

Open
malcolmstill opened this issue Sep 4, 2020 · 1 comment
Open

Per-client resource allocation? #43

malcolmstill opened this issue Sep 4, 2020 · 1 comment
Labels

Comments

@malcolmstill
Copy link
Owner

As it stands:

  • all foxwhale resource allocation (juxtaposed to the allocation of object ids) occur at a global level
  • if we out-of-memory (OOM) the client that happens to hit the OOM will be killed.

I was thinking that perhaps resources should be allocated on a per-client basis. This would mean the greedy client would get killed, with the added complexity (is it actually more complex) would get killed. Which would be nice.

@malcolmstill
Copy link
Owner Author

With the above said, I am wondering whether to keep the global allocation, but rather than just killing the client that see the OOM, could we go out of our way and find the client that is misbehaving and kill that instead.

That seems nice, but that would introduce the complexity of having the client that innocently hit OOM somehow rerun whatever was attempting to allocate memory in the first place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant