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.

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

Jump to bottom

Special case node in both compute/client and storage roles #3251

Closed
kostko opened this issue Sep 8, 2020 · 0 comments · Fixed by #3745
Closed

Special case node in both compute/client and storage roles #3251

kostko opened this issue Sep 8, 2020 · 0 comments · Fixed by #3745
Assignees
@jberci
Labels
c:performance Category: performance c:runtime/compute Category: runtime compute worker c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Sep 8, 2020 •
edited
Loading

When the local node is both a storage and compute (or client) node, all storage operations should be tried on the local node first as an optimization.
@kostko kostko added c:runtime/compute Category: runtime compute worker c:storage Category: storage c:performance Category: performance labels Sep 8, 2020
@kostko kostko mentioned this issue Jan 28, 2021
Open
@kostko kostko changed the title Special case node in both compute and storage roles Special case node in both compute/client and storage roles Feb 17, 2021
@jberci jberci mentioned this issue Mar 2, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jberci jberci

Labels
c:performance Category: performance c:runtime/compute Category: runtime compute worker c:storage Category: storage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go/worker: Make compute and client node use local storage if available oasisprotocol/oasis-core
2 participants
@kostko @jberci