Evaluate Profile-Guided Optimization (PGO) on the library
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
Recently I tested a lot of software with PGO and measured the performance improvements from PGO - the results are here. Since my results show interesting improvements on a lot of databases I think it would be a good idea to measure PGO effects on SplinterDB as well. If the results will show an improvement - would be great to see a note in the documentation about PGO.
Since SplinterDB is a library, I think the most interesting experience for you will be my results on optimizing SQLite with PGO (see in the linked above repo as well).
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 reviewing the PGO results in the linked awesome-pgo repository and determine how to measure PGO effects on SplinterDB. Done means producing comparable results for the library and, if they show an improvement, adding a note to the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100