Skip to content

Issues: bbThemis/ThemisIO

Beta
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

6 Open 0 Closed
6 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

ThermisIO has a heavy weight implementation, using client processes, servers and a file system (that stands over burst buffers). The overhead is not presented and it is not clear how this will scale.
#10 opened May 11, 2022 by zhaozhang
Call it out "an opportunity of fair-sharing rather than an mandatory I/O bandwidth assignment as in previous works"
#9 opened May 11, 2022 by zhaozhang
@zhaozhang
There are comparisons between exclusive access and fairness-enforced access, but not between Themis and simple (un-intercepted) Lustre I/O.
#8 opened May 11, 2022 by zhaozhang
@zhaozhang
Run ThemisIO on nvdimm nodes.
#7 opened May 11, 2022 by zhaozhang
@zhaozhang @wangyinz
it is unclear how ThemisIO scales with size of deployment and number of IO requests
#6 opened May 11, 2022 by zhaozhang
@zhaozhang @wiliamhuang
limited evaluation (only 4 compute nodes and up to 2 Themis nodes) that does not allow to assess the efficiency and scalability of ThemisIO on real systems. For instance, the need to have a global state among all ThemisIO servers, might become a bottleneck
#5 opened May 11, 2022 by zhaozhang
@zhaozhang
ProTip! What’s not been updated in a month: updated:<2025-03-28.