after installing Compute Visual Profiler,
I open it with this error:
Unable to load the 'nvcuda' library.
Computer Visual Profiler device features will be disabled.
My computer does not have NVIDIA graphic card. Would it be a problem causing this issue?
Thanks in advance.
The Visual Profiler is designed to execute programs and collect profile data, it's looking for the NVIDIA driver and when it can't find the driver it tells you. You should still be able to use the Visual Profiler to load projects created on other machines with CUDA capable GPUs.
Related
Here is a window from the Nvidia Nsight visual Studio edition.
I am trying to analyze my CUDA code, but I use the Nvidia Nsight Eclipse Edition. Can someone please tell me how do I get such information in the Eclipse edition? I searched and searched, but could not find any way. This question may appear to be very naive, but it has got me really frustrated.
Thanks!
You can get these metrics details by NVIDIA Visual Profiler directly by collect metrics. Also the visual profiler can be triggered also from Nsight Eclipse Editon by setting Profile configurations.
I'm trying to set up a cuda development environment under windows, and lurked many cuda-tagged posts, but few things are still unclear:
Can I debug cuda applications under windows without the need of a second video card, using nsight and VS2010 express?
Can I debug cuda applications under linux without the need of a second video card, AND without shut down the graphical interface?
Answered thousands of times, but perhaps something has changed, so I ask again just to be sure: Can I develop under windows without installing a cuda-enabled video card? There is some kind of emeulator? (Ocelot for windows is practically inexistent).
Thanks.
Can I debug cuda applications under windows without the need of a second video card, using nsight and VS2010 express?
You can apparently debug with a single video card, but nsight requires vs2010 professional (not express edition)
https://developer.nvidia.com/nsight-visual-studio-edition-requirements
Can I debug cuda applications under linux without the need of a second video card, AND without shut down the graphical interface?
I don't think so, from the eclipse nsight docs (http://docs.nvidia.com/cuda/nsight-eclipse-edition-getting-started-guide/index.html#linux-requirements):
"A GPU that is running X11 (on Linux) or Aqua (on Mac) cannot be used to debug a CUDA application and will be hidden from the application ran in the debugger. Such GPU can still be used for profiling GPU applications."
Answered thousands of times, but perhaps something has changed, so I ask again just to be sure: Can I develop under windows without installing a cuda-enabled video card? There is some kind of emeulator? (Ocelot for windows is practically inexistent).
no, if you want to use cuda, you'd be best off just getting a cheap cuda-enabled card (e.g. a GTX 650 is ~$100 and is the most recent (kepler) architecture)
Does anyone know if its possible to Debug CUDA using parallel NSight on a remote machine? I am able to step into CUDA code but not my host code. It says CUDA has the capability to generate host debug information so debugging remotely and locally should be possible.
My card is a 580 GTX.
//device code <-- able to debug device code
//host code <---- when device code returns, should be able to debug host code
Thanks!
Simultaneous GPU/CPU debugging from a single IDE instance is unfortunately not possible with the current releases of Nsight and Visual Studio.
As a workaround, you can start GPU debugging from one copy of Visual Studio, then open a second IDE instance and attach its CPU debugger. They won't have unified stepping, but you can at least set breakpoints independently.
It should now be possible to attach both the Visual Studio default debugger and NSight in the same VS instance. Then this should work.
I have installed Parallel Nsight for Visual Studio 2010. Due to my research, it is not able to debugging on machines which dont have NVIDIA graphic card.
Therefore, I would like to debug it on the server (connecting to the server), would it be possible?
Thanks in advance.
Yes. You can install Visual Studio and Parallel Nsight on your developer machine, and install Parallel Nsight on the remote machine with the GPU. Then you simply configure Parallel Nsight to execute on the remote machine.
Behind the scenes, when you "start CUDA debugging", Nsight will copy the executable (and any specified data files) to the remote machine and launch the task.
See the Parallel Nsight website for more details and to check system requirements, as well as the documentation that is installed.
So I have successfully installed the CUDA toolkit and GPU computing SDK on a Mac Pro running OS X version 10.6.6. The sample CUDA programs provided with the SDK as well as some programs of my own work well. However, when I run any of these CUDA programs through the NVIDIA Visual Profiler (the executable is called computeprof), I always get the following error upon launch:
"Unable to initialize the Profiling in Start/Stop mode"
NVIDIA's documentation does not mention this error, and Googling shows a single post in the NVIDIA forums in which several people have run into this problem recently (since October 2010) but no solutions.
Any information on this error message would be greatly appreciated.
If Visual Profiler v4.0 isn't working for you, there's a new CUDA release out (v4.1) and it includes a completely new & re-designed Visual Profiler.
The new NVIDIA Visual Profiler (v4.1) supports automated performance analysis to identify performance improvement opportunities in your application. It also links directly to the most useful sections of the Best Practices Guide for the issues it detects. And the Visual Profiler is available for free as part of the CUDA Toolkit on NVIDIA's developer web site: http://www.nvidia.com/getcuda.
If you experience any problems, please file a bug via your (free) NVIDIA registered developer account so the team working on the Visual Profiler can figure out the problem.
Are you using CUDA4.0?
I had problem with CUDA 4.0 and visual profiler (I use a Linux system). But it works fine with CUDA 3.2.