CPU usage at 100% of a core multiple times a day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by profiling the process during the reported CPU spikes and trace which task is consuming a core when no calendar changes are being synced. The issue names no files or tests; identify the hot path and reproduce the repeated spikes before proposing a fix. Done means CPU use no longer stays near a full core for several minutes without sync activity.
Written by the indexing model from the issue text.
Description
Multiple times a day the process uses up 100% of a core for several minutes and causes my laptop to get hot. This is despite no calendar changes having been made in the interim, so I don't understand why it's so CPU intensive when nothing is getting synced.
- Dominant language
- Python
- Stars
- 332
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from etesync/etesync-dav
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
etesync/etesync-dav#376 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
etesync/etesync-dav#371 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
etesync/etesync-dav#355 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
etesync/etesync-dav#375 · 1 reaction ·
-
PROPFIND on user home returns 500: `ValueError` in radicale `xmlutils.make_clark` (meta keys without `prefix:tag` form)Possibly taken @vitlav claimed this 36 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
etesync/etesync-dav#372 ·
All issues in etesync/etesync-dav
Similar issues
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Switch to ruffOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Qiskit/qiskit-aer#2533 ·
Maintainers usually reply within 1 day
-
crate-drift
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
po4yka/rust-skills#33 ·
Maintainers usually reply within 1 day