Performance observation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
I have a very sluggish Deck installation.
I noticed what takes the most time is the /ocs/v2.php/apps/user_status/api/v1/statuses/<user> requests. For 5 users I get like 50 requests. Same number of the cards the users are assigned to maybe? Each request takes about 1-2 seconds on my Hetzner instance.
Thought I'd mentioned this in case there's a way to cache them and improve performance.
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 reproducing the reported requests to /ocs/v2.php/apps/user_status/api/v1/statuses/ with five users and measure request count and latency. Trace where Deck triggers these requests, then verify that any caching or request reduction preserves current user-status behavior and improves the reported performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100