getappmap / getappmap/appmap-js
High CPU and memory usage with AppMap scanner CLI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
I tested https://github.com/TooTallNate/Java-WebSocket/tree/master with the JetBrains AppMap plugin (0.48.0)
Setup:
- Windows 10 in a VM
- IntelliJ Ultimate 2021.3
- AppMap plugin 0.48.0
- Repository: https://github.com/TooTallNate/Java-WebSocket/tree/master. I recoreded AppMaps of
mvn installin a previous session. I launched the IDE and opened the project with the existing AppMaps.
The machine had a very high memory usage for the scanner and also constantly high CPU usage (consuming 1-2 CPU threads). The usage didn't go down after waiting for about 15 minutes. AFAIK the AppMaps were already indexed and scanner in the previous session of the IDE, AFAIK. I'm not sure why the scanner is apparently working on it again...
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 report with the Java-WebSocket repository, Windows 10 VM, IntelliJ Ultimate 2021.3, AppMap plugin 0.48.0, and previously recorded AppMaps. Investigate why the scanner continues consuming high CPU and memory after reopening an already indexed project; done means existing AppMaps do not trigger sustained rescanning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- cli, devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100