Here is a list of the limitations:
- Once connected to a remote target, all the Browse buttons in the GUI will remain disabled. You can copy/paste or type the URI paths wherever required.
- If you have not closed the GUI after profiling locally and try to connect to Remote Target, the GUI may crash sometimes. Hence, it is recommended to close the GUI after local profiling if remote connection is desired.
- If local data is not required and you try to connect to the same remote target
frequently, use the following command to directly connect to the remote target (if
it is
running):
AMDProfilerservice <ip_address> <port>For example,
AMDProfilerservice <ip address> 32768 - A client (GUI instance) can connect to a AMDProfilerService instance. However, if multiple instances of the GUI are launched by a user, only one will succeed. Different users can connect to the same AMDProfilerService as they will have different client IDs.
- Multiple instances of AMDProfilerService can be launched. However, all of them must be on different ports even if they are bound to the same IP address.
- Remote profiling connection establishment might fail if the target system firewall is enabled. In such cases, disable the firewall or add an exception for AMDProfilerService in the firewall rules of the target system and try reconnecting. Another reason for failure could be unavailability of port number. This can happen due to network configuration, firewall settings, or another program blocking usable ports.
- Profiling of MPI applications is not supported with remote profiling.