oasisprotocol / oasisprotocol/oasis-core
perf: multithreading within an enclave
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Find ways to multi-thread in the compute node.
Currently, request decryption, request processing, and response/state encryption happens in a single thread. We should be able to multi-thread aspects of the core trusted Ekiden library to speed some of these parts up
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies request decryption, request processing, and response/state encryption in the compute node and trusted Ekiden library as the affected areas. Start by tracing those paths and determining safe concurrency boundaries. Done means the relevant work can run across multiple threads without compromising enclave behavior, with a measurable performance improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100