When you close the session, you can save the session settings (filter, profiling and triggers settings) so that you can reuse them for future use. When you attach to the same application again, start the saved session instead of using "Quick attach". Of course you can also start out by creating such a dedicated session in the first place.
In this case, invoke Session->Quick Attach from the main menu and select "On another computer". Click [Edit] to configure the SSH connection and make sure to keep the "Discover running JVMs and attach to selected process" option on the "Configure SSH tunnel" step of the wizard selected.
After the SSH connection has been established, JProfiler will then
Similar to the "Locally running JVM" case above, you can then select the JVM from the list of discovered JVMs. In addition, the selection dialog allows you to change the user that is used for detecting JVMs.
In your local JProfiler GUI, create an "Attach to remote JVM" session and enter the host name and the same profiling port that you specified in jpenable on the remote machine. When you start the session, it connects to the remote JVM and you can start profiling.
Alternatively, invoke Session->Quick Attach and select the "On another computer" option that will allow you to enter your remote connection details without configuring a session. When you close the session, you will then be asked whether to save it or not.
When you choose "Dynamic instrumentation" as the method call recording type, it is important to choose profiled packages that focus on the classes of interest. In that way, relatively few classes are instrumented. Alternatively, you can choose Sampling in the profiling settings.
If JProfiler detects that the PermGen space would be overloaded with the current filter settings, it will warn you in the session startup dialog. You should then switch to sampling or define narrow set of profiled packages. Clicking on the hyperlinks in the warning message will quickly make these changes. When selecting profiled packages, the total amount of instrumented classes is monitored and you are notified if you exceed the approximate maximum number of classes that can be instrumented.
By default, array allocations are not recorded in attach mode, although the session startup dialog gives you the possibility to do so for "non-client" JVMs (the "client" JVM has a bug that prevents this from working successfully).