oasisprotocol / oasisprotocol/oasis-core
Standardized storage block/page size?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
In filesystems you have the notion of a fixed filesystem block size (different from blockchain blocks), so reads and writes to actual data occur at that granularity.
In our current system, we are operating at the granularity of k/v pairs, which could be of variable size.
The question is, is it worth imposing a standard chunk size?
e.g. we could merge multiple values to a single block, or split a large value into multiple blocks
It depends on the driver, it might be different if we use IPFS vs AWS S3 vs AWS dynamo vs BitTorrent DHT vs libtorrent (edited)
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
No files, tests, or entry points are named. Start by locating the storage-driver abstraction and comparing the listed IPFS, AWS S3, AWS Dynamo, BitTorrent DHT, and libtorrent options; done means the project has decided whether to standardize chunk sizes and documented the driver-specific scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100