getappmap / getappmap/appmap-js
High CPU usage with appmap-linux
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
I ran AppMap with IntelliJ on an internal project.
The following command was launched by the AppMap plugin. The process consumed roughly one to two complete CPU threads. CPU usage did not go down, but I expected it to go down because there were no file changes in the watched directory.
If you need the log file of verbose output, please ask me on Slack for /home/jansorg/temp/bashsupport-pro-appmnap/appmap-linux.log.
/home/jansorg/self-employment/customers/AppLand/intellij-plugin/build/idea-sandbox/system/tmp/appland-downloads/appmap/3.89.1/appmap-linux-x64 index -v --watch --appmap-dir /home/jansorg/temp/bashsupport-pro-appmnap/build/appmap
# find . -iname \*.appmap.json | wc -l
210
# du -hs --apparent-size build/appmap/
2,0G build/appmap/
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 command with --watch against the build/appmap directory containing about 210 files and 2.0G of data, then observe CPU usage when no files change. Review the verbose output in appmap-linux.log if it is available; done means CPU usage no longer remains at one to two threads while the watched directory is idle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100