Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

Problem: unnecessary extra thread for TDBE<->chain-abci exchanges #2191

Open
tomtau opened this issue Aug 26, 2020 · 0 comments
Open

Problem: unnecessary extra thread for TDBE<->chain-abci exchanges #2191

tomtau opened this issue Aug 26, 2020 · 0 comments
Assignees
Milestone

Comments

@tomtau
Copy link
Contributor

tomtau commented Aug 26, 2020

instead of current two threads ("chain-abci" and "persistence"), it could just be one. instead of taking Storage, it'd take some subset (some new definition) that can do the lookups (like ReadOnly) + only modify certain parts (exposed by some methods) and immediately flush.
enclave protocol will need extra definitions for this unified TDBE<->chain-abci communications
and the other enums/structs (IntraEnclaveRequest for TVE, EnclaveRequest for TQE...) can be renamed to better reflect which enclave they are meant to interface with

@tomtau tomtau added this to the CRO Sprint 38 milestone Aug 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants