nextcloud / nextcloud/whiteboard
High CPU usage since AIO v12.5.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
I've been experiencing high CPU usage from nextcloud, and looking at docker stats it's clear that the whiteboard container is responsible. CPU usages ramps up then comes back down around every ~6 seconds.
The redis-server container's CPU usage also mirrors the peaks and valleys of the "MainThread" of Whiteboard, i'm assuming whiteboard is stuck in some loop and part of that loop is getting something from redis.
The PID of MainThread doesnt change, so it seems something inside the process is looping, rather than the whole process (or even the container) being recreated.
top from the nextcloud VM:
docker stats from the nextcloud VM:
top from inside the whiteboard container (cpu doesnt seem high at all):
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 periodic CPU peaks reported for the whiteboard container after AIO v12.5.0, using docker stats and the MainThread and redis-server observations in the issue. Trace the recurring activity to its source; done means identifying and resolving the loop or operation responsible for the roughly six-second CPU cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, redis
- Domain
- backend, infrastructure, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100