Improve Validation Performance
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 35
- Forks
- 17
- Avg merge
- 48m
- Merged PRs (30d)
- 10
Description
As Language will replace the validation logic on the server, any performance issues will directly impact OpenFGA users.
We will need to run a performance benchmark and optimize our validation code so as not to introduce any unnecessary delay, something we are not optimizing properly for currently.
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 names no files, tests, or entry points. Start by locating the validation logic and identifying how validation is currently measured, then establish a performance benchmark before considering optimizations. Done means benchmark results demonstrate that validation adds no unnecessary delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100