perf: collect production profiles to enable PGO
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.3k
- Forks
- 488
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 11
Description
Profile Guided Optimization can significantly improve performance of Go programs.
To enable this optimization, we need to continuously collect profiles from a production environnement.
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 with the issue’s Go PGO documentation link and inspect the repository for existing production profiling or deployment entry points. Define how profiles should be collected continuously and made available for PGO; done means a documented, working production collection process integrated with FrankenPHP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100