NFDI4Energy / NFDI4Energy/SMECS
Check performance of backend
Open
Nobody has claimed this yet.
back end
mid-term
- Dominant language
- Python
- Stars
- 13
- Forks
- 1
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 1
Description
The backend does multiple calls to external APIs. We should get an overview how many calls are done and how much data is received to analyze what can be optimized.
Ideally an automatic check on this topic is done for each Pull Request.
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.
Research direction
Start by locating the backend code that makes external API calls and the repository's pull-request checks. Measure the number of calls and amount of data received, then determine how those measurements should be reported automatically for each pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, ci-cd, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100