parse-community / parse-community/parse-server
Add CI check for performance impact
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Currently, changes in Parse Server are not evaluated based on their Parse Server performance impact. This can lead to "hidden" degradation of Parse Server that won't be discovered for a long time. When a performance issue is discovered, it is usually hard to pin down the root cause in retrospect.
Feature / Enhancement Description
Add CI check that evaluates performance impact.
Example Use Case
n/a
Alternatives / Workarounds
Unknown
3rd Party References
Unknown
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 by reviewing the repository's existing CI checks and how Parse Server performance is currently evaluated, if at all. Define what performance impact should be measured and what constitutes an acceptable result; done means the CI process reliably detects regressions without requiring retrospective investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, ci-cd, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100