Consider caching algorithmic improvement
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
A novel lightweight but efficient caching algorithm:
https://www.usenix.org/publications/loginonline/sieve-cache-eviction-can-be-simple-effective-and-scalable
OpenSSL has quite a number of caches all over the place and we might gain some benefits from this.
It also ought to be possible to implement this in a lockless fashion using atomic operations.
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
Start by reading the linked SIEVE cache article and reviewing the caching areas across OpenSSL. The issue does not name a target cache, entry point, benchmark, or acceptance criteria, so define the affected cache and measurable performance goal before implementation; done would require an agreed design and evidence of improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100