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

Customized I/O buffering policy with Hermes Blobs control #493

Open
mengtang-pnnl opened this issue Feb 21, 2023 · 0 comments
Open

Customized I/O buffering policy with Hermes Blobs control #493

mengtang-pnnl opened this issue Feb 21, 2023 · 0 comments

Comments

@mengtang-pnnl
Copy link
Contributor

Hi, I understand that we are able to give Hermes blob a score to hint at the blob's importance. Since a Hermes blob is great granularity for what a customized buffering policy can control, we would like to know if it is possible for Hermes to expose some mechanisms for controlling

  1. where a blob should live in the tier
  2. where a blob should go next (e.g. can we provide some control over expected RPCs/network messages?)

My understanding from the wiki is that operators like MOVE(BufferID, TargetID) and COPY(BufferID, TargetID) can control a blob's tier. And we would also like to control a blob's location with respect to compute nodes.

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

No branches or pull requests

1 participant