Performance issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- api, performance
Research direction
Start by locating the Evaluate API entry point and determine how to reproduce the reported performance behavior. Exercise it with 100 flags concurrently and measure response time. Done means the API responds within 3 seconds consistently; further details are still needed from the issue.
Written by the indexing model from the issue text.
Description
Flakey performance has been observed in the Evaluate API.
Expected behavior
Evaluate API should respond within 3 seconds for 100 flags concurrently
More details to follow
- Dominant language
- C#
- Stars
- 50
- Forks
- 19
- Avg merge
- 8d 16h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/FeatureFlightingManagement
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation
microsoft/FeatureFlightingManagement#33 · 1 assignee ·
-
performance issue
microsoft/FeatureFlightingManagement#26 · 1 assignee ·
All issues in microsoft/FeatureFlightingManagement
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·