YourKit Manually Configure Target JVM for Remote Profiling: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
Start the JVM with the following configuration: | Start the JVM with the following configuration: | ||
java ... -agentpath:<profiler-agent-path>[=options] ... | java ... -agentpath:<''profiler-agent-path''>[=''options''] ... | ||
Linux example | Linux example | ||
java ... -agentpath:<profiler directory>/bin/linux-x86-64/libyjpagent.so | java ... -agentpath:<''profiler-directory''>/bin/linux-x86-64/libyjpagent.so | ||
To check that Java can load the profiler agent, run: | To check that Java can load the profiler agent, run: | ||
java -agentpath:<profiler-agent-path>=help | java -agentpath:<''profiler-agent-path''>=help | ||
=Options= | |||
Example: | |||
java ... -agentpath:<''profiler-agent-path''>=alloceach=10,allocsizelimit=4096 ... | |||
Revision as of 00:21, 9 June 2018
External
Internal
Overview
Start the JVM with the following configuration:
java ... -agentpath:<profiler-agent-path>[=options] ...
Linux example
java ... -agentpath:<profiler-directory>/bin/linux-x86-64/libyjpagent.so
To check that Java can load the profiler agent, run:
java -agentpath:<profiler-agent-path>=help
Options
Example:
java ... -agentpath:<profiler-agent-path>=alloceach=10,allocsizelimit=4096 ...