The visual profiler uses the same performance counters that are available in the command line profiler (see the “CUDA_Profiler” file in the CUDA doc directory).
The profilers can’t automatically calculate GFLOPs performance, for that you need to count the number of FLOPs in your kernel.
The profilers can’t automatically calculate GFLOPs performance, for that you need to count the number of FLOPs in your kernel.
[snapback]392605[/snapback]
I was afraid of that. This method is very impractical for large software with many large arithmetically intense kernels.
Is this a feature/problem that anyone else is looking at for the moment?
e.ping
June 13, 2008, 9:01pm
63
this doesnt seem to work for me. i get:
=== Start profiling for session 'Session1' ===
Start program 'D:/program/MATLAB/R2007b/bin/matlab.exe' run #1 ...
Program run #1 completed.
Start program 'D:/program/MATLAB/R2007b/bin/matlab.exe' run #2 ...
Program run #2 completed.
Start program 'D:/program/MATLAB/R2007b/bin/matlab.exe' run #3 ...
Program run #3 completed.
Error -94 in reading profiler output.
Minimum expected columns (method,gputime,cputime,occupancy) not found in profiler output file.
i run win xp pro, and as can be seen form the output i use matlab r2007b.
any suggestions?
[snapback]377235[/snapback]
Adding the “quit” command at the end of Matlab script will remove this error.
Unfortunately not right now, unless you can generate an executable from the matlab code (I think matlab can do this, but I’m no expert).
I have already filed a feature request for profiling external programs as is supported by some CPU profilers.
Mark
[snapback]313276[/snapback]
i think the profiler shoud also show the time taken by individual functions for a kernel as kernel can be quite complex and optimizing it is very tough job…
Just my guess but it seems that would be hard to do seeing that functions inside a kernel are inlined.
:huh:
I have declared all the functions used by my kernel to be noinline
I think that is ignored by the compiler. Functions are always inlined.
gpugpu
July 14, 2008, 1:41am
68
Is there any command-line profiler available for cuda?
Thanks.
espe
July 31, 2008, 10:13am
69
Is there any tutorial on how to use this tool?
defy
August 14, 2008, 11:47am
70
Hi!
I’m using CUDA 2.0 Beta2 on Vista 32.
Whatever I do with profiler I can’t manage it to show counters (gld coalesce, gld uncoalesce …) .
I only see the Method,GPU time,CPUtime,Occupancy columns.
Is it possible to get other data?
Hi!
I’m using CUDA 2.0 Beta2 on Vista 32.
Whatever I do with profiler I can’t manage it to show counters (gld coalesce, gld uncoalesce …) .
I only see the Method,GPU time,CPUtime,Occupancy columns.
Is it possible to get other data?
[snapback]425535[/snapback]
Profiler counters and timestamps are currently not supported on Windows Vista. (This is mentioned under the “known issues” section of the Windows release notes.
Well, considering that you cannot buy WinXP anymore ( it reached 2-months ago its end-of-selling period ), I would say to add full Vista compatibility to the profiler it should be a priority. Do you plan to release a patch soon for the timestamps and counters, pls?
chrismc
September 9, 2008, 1:15pm
73
I’m having trouble with the profiler.
See [url=“The Official NVIDIA Forums | NVIDIA ”]http://forums.nvidia.com/index.php?showtopic=76838[/url]
my sytem is 64 bit linux/SUSE Enterprise 10.1
chrismc
September 9, 2008, 1:24pm
74
PLEASE IGNORE.
I’ve just found I need to add -noprompt in the arguments box of session settings.
not8
October 8, 2008, 4:47am
75
Well, considering that you cannot buy WinXP anymore ( it reached 2-months ago its end-of-selling period ), I would say to add full Vista compatibility to the profiler it should be a priority. Do you plan to release a patch soon for the timestamps and counters, pls?
[snapback]426715[/snapback]
I would also greatly appreciate Vista support for the profiler.
Vista support would be great!
Need timestamps and counters immediately, but i have onlv Vista.
Shall I install XP or wait for the next Release of the Profiler?
You can profile a mex file with the CUDA profiler, if you have a matlab script with no gui.
Just follow these steps in the session setup.
in Launch specify “/usr/local/bin/matlab”
In Working directory select the directory of your matlab script
in Arguments: -nojvm -nosplash -r name_of_matlab_script (with no .m)
Start the profiler.
It worked fine for me under Linux.
In Windows you need to have the -wait option in the arguments, but -nojvm and -nosplash are not required (though will cut down on overhead).