open-feature / open-feature/flagd
Performance benchmarking framework and CI gating
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Context
At KubeCon EU 2026, the flagd discussion (recap) identified the need for a structured approach to performance testing.
Problem
There's currently no standard way to measure flagd performance across changes, and no CI mechanism to catch performance regressions before they're merged.
Proposal
- Establish a performance benchmarking suite for flagd core evaluation paths
- Integrate benchmarks into CI so PRs can be gated on performance regressions
- Define baseline metrics for evaluation latency, throughput, and memory usage
- Explore CNCF support for running benchmarks on dedicated machines to get consistent results
Related
- #1772: Set coverage thresholds for bug-fixes and new features
- #1774: Review gherkin suite and test-harness for missing test coverage
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
The issue does not name files, tests, or entry points. Start by locating flagd's core evaluation paths and existing CI configuration, then review related issues #1772 and #1774. Done means a benchmark suite, baseline latency, throughput, and memory metrics, and a defined CI gating approach, with dedicated-machine support evaluated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100