Type: New Feature
Affects Version/s: 1.3.3
Fix Version/s: None
It would come in very handy if one could instruct VisualVM to start sampling/profiling a java process right away that has been given by the already existing --openid command line option.
This could be implemented as a new option --autostart with values like "cpu-sampling", "memory-sampling", "cpu-profiling" etc.
This new feature could then be used in the eclipse launcher so that you don't have to switch over to VisualVM and start sampling/profiling manually. This manual activation is quite cumbersome and you might click the respective button too late (in case of rather short running JUnit tests and the like).
For a clean integration in eclipse, one should be able to configure this "autostart" behaviour on a "per run configuration" basis but I don't know if this can be achieved easily. YourKit has an integration like that, for example.
To make this scenario complete, another command line option could be introduced to pre-select a VisualVM profile (e.g. --profile).
Btw: I couldn't find a description of all command line options in the documentation that are available today, so maybe a page for that should be added.