Feature request: remote instrumentation profiling
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
The generations count feature of the instrumentation memory profiler is the fastest way to identify a memory leak. It's useful to be able to attach to a remote JVM in dev/QA envs to check this, there are environments where running VisualVM on the remote machine is not possible.
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 with VisualVM's instrumentation memory profiler and its generations count feature, then trace how it attaches to a local JVM. Determine the supported way to attach to a remote JVM in development or QA environments and define how generations profiling should work there. Done means the remote profiling workflow is implemented and verified without requiring VisualVM to run on the remote machine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100