wpilibsuite / wpilibsuite/SystemcoreTesting
High Systemcore cpu utilization from REV HW Client
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 186
- Forks
- 24
- Avg merge
- 8h 27m
- Merged PRs (30d)
- 9
Description
The 5 "CAN Send Thread"s are using ~6% (of a single cpu core) each, for a total of 6-8% overall cpu utilization. REV HW client is not active, this is out of the box idling. Motioncore is attached, but no devices are plugged in.
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 reproducing the reported idle setup with Motioncore attached, no devices plugged in, and REV HW Client inactive. Inspect the five CAN Send Threads and compare their CPU use with the report's roughly 6% per thread; done means the unexplained idle utilization is understood and the regression is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- embedded-iot, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100