I am working on a M1 MacBook (with Arm architecture). My OS is Big Sur 11.2.3.
I have installed Nsight Compute on my machine and followed the suggestion in this thread.
I can start Nsight Compute but when I try to launch a process on a remote machine Nsight Compute hangs (I see a spinning wheel and an Application Not Responding message).
I do not have any difficulty logging in to the remote machine using a Terminal window and running the process through the Terminal.
I am accessing the remote machine through a VPN connection.
We have so far been unable to reproduce the issue internally on a similar setup (Big Sur 11.2.2). Can you share more details, e.g. about the the type of target system you are connecting to? Do you use the Profile activity, or the Interactive Profile activity? Does the remote file selection dialog work for you?
type of target system you are connecting to?
Linux machine running Ubuntu 16.04.6 LTS
Do you use the Profile activity, or the Interactive Profile activity?
I have tried both and I get the same issue with each of them.
Does the remote file selection dialog work for you?
No. When I click on the little box with 3 dots on it to browse the remote file system a box appears telling me “Connection failed!”. The box asks me for my User Name and Password. When I enter these and click OK then Nsight Compute hangs.
In terms of what I can do now to profile applications running on a remote machine, the following works for me:
- Use the Connect to process GUI to set arguments for Profile Activity.
- Copy-Paste the text in the Command Line box into a Terminal window that is logged into the remote machine.
- Run NVIDIA Nsight Compute CLI (ncu) on the remote machine and write the output to a network drive that is mounted on my local machine.
- Open the output file in Nsight Compute on my local machine for analysis of the profiling results.
I would still like to be able to use the GUI version of Nsight Compute. For example, in the past I have found graphical debuggers very useful (e.g. in Visual Studio code).
Have you verified that the necessary ports as shown in the message or the tool’s options dialog are accessible between these two systems? For Nsight Compute, this means at least port 49152 (unless it’s already used by some other application on the target system).
You can also try to attach by launching the application using the ncu command line on the remote target with the --mode launch flag and then attaching with the interactive activity from the host UI. Likewise, the necessary port(s) need to be accessible for this to work.