transparency-dev / transparency-dev/incubator
[VIndex] Need a faster implementation of disk-based storage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 6
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
The current implementation of the verifiable index doesn't scale to CT-size logs. Or rather, the number of keys that indexing CT generates.
The in-memory version requires too much RAM, and the disk-based version isn't fast enough to process this many entries in a reasonable timeframe.
There is a faster version in progress, and we should incorporate that eventually.
In the meantime, we need some way to cut down CT indexing to a reasonable size. Options:
- MapFn that outputs only a deterministic subset of entries (e.g. only those for certain domains, TLDs, or some other predicate)
- Create a local log with a reasonable number of entries populated from a prod log
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the current verifiable-index implementation and the linked mpt/DESIGN.md proposal. Determine whether the project will pursue a deterministic MapFn subset or a local log populated from a production log, then define a measurable CT-indexing size and processing-time target. Done means the selected approach makes CT-scale indexing reasonable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100