Guidelines - performance (P1)
Open
Nobody has claimed this yet.
essnmx
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
Investigate if the workflow(s) are performant enough to handle the event rates expected for this technique.
See P1 in the guidelines
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 P1 in the linked reduction-workflow guidelines and identify which workflows are covered by this issue. Assess whether they handle the expected event rates; the work is done when their performance has been evaluated against those expectations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100