Power profiling can be enabled:

1. On the second wizard page when creating a new session.
2. From the "Settings" view under the session timeline view.

Power profiling is not available for all devices and does not work on Mac OS X.

Update from @ahmad:

Oh, I found the problem. I was running win32 binary on 64-bit operating system. This is why the profilers do not report power, while every other profiling facilities work. Please add this issue to your answer, so we can mark this question answered. Thanks again.

Nsight Visual Studio Edition 2.2 offers the following advantages over the Visual Profiler:

OVERALL

1. Integration into Visual Studio 2008 SP1 and 2010 (requires Professional Edition as VS Express Edition does not support integration packages).

2. Local and remote analysis sessions. Remote sessions can also be configured to copy the application and resources to the remote system.

3. Collect information from a target application or from a process tree.

4. Report views support more advanced grouping and filtering. Data tables can be exported to excel.

TRACE ACTIVITY

1. Trace OS activity including process, thread, and module lifetime, thread context switching, thread wait reasons, CPU utilization, process CPU utilization, and thread utilization.

2. Collect API and GPU work trace for CUDA, OpenGL 2.x-3.x, DirectX 9-11, and OpenCL 1.1 and show all information on the timeline.

3. Collection of call stack traces on all traced API calls or only when traced API calls return errors.

4. CUDA software counters to show allocated memory per context.

5. Additional control over what information is traced. This is critical as tracing too much information can cause the application to become CPU bound.

6. Timeline and tree display for user annotations from NVIDIA Tools Extensions Library and D3D Performance Markers.

CUDA PROFILING ACTIVITY

1. The CUDA profiler provides a method to capture your kernel and replay it many times transparent to your application. This allows collection of profiling data in non-deterministic applications and with only 1 launch of your applications. The Visual Profiler <= 5 requires the application to be deterministic so that it can relaunch the application many times.

2. Supports collection of many useful metrics not yet support by the Visual Profiler including warps eligible which is the most critical metric for understanding if you have sufficient occupancy and warp stall reasons to help you understand what is limiting the performance of the application.

The Visual Profiler has the following advantages:

1. Cross platform.

2. Provides expert system to review the collected information.

3. Links in the results to the CUDA Best Practices Guide.

4. Timeline can show correlation between CPU and GPU events when you click on an event.

5. CUDA 5.0 supports new command line profiler (nvprof).

6. CUDA 5.0 supports source correlation for branch divergence and memory access with bad access patterns.

7. CUDA 5.0 profiler is integrated into Nsight Eclipse Edition.

8. Better support for Tesla PM counters.

Visual Profiler in CUDA 5.0 adds a number of the features available in Nsight 1.5 and 2.x including

• NVIDIA Tools Extension Library for annotating your application with ranges and markers that can be displayed in the timeline.

• Concurrent kernel trace on Fermi and Kepler GPUs.

Both tools will provide your very helpful information for analyzing your application. I recommend that you use the latest version of each of the tools.

The upcoming version of Nsight VSE will have many new features for investigating the execution of your CUDA kernel. For more information see http://developer.download.nvidia.com/GTC/PDF/GTC2012/PresentationPDF/S0430-GTC2012-Developing-CUDA-Nsight.pdf.