Aleksandar
01-31-2012, 01:51 PM
Hi All,
Profiling is a very important process in software development. Dealing with multithreaded execution in a multi-core preemptive environment, that dynamically changes its performance state during execution, is quite challenging to be accurately profiled; but that is exactly what should be done with all graphics applications.
Before delving deeper into the topic, I would like to hear from you guys, what profiler are you using for developing OpenGL based applications?
Here is a short list of possible profilers:
- gDEBugger
- AMD gDEBugger - Visual Studio 2010 Extension
- AMD GPU PerfStudio 2.8
- NVIDIA Parallel Nsight
- NVIDIA Platform Analyzer (NPA)
- VSProfileLib – Very Simple Profile Library
Please broaden the list with other profilers that support OpenGL. NPA doesn't directly supports OpenGL, but it can be used for profiling GPU processes. Also, NV Parallel Nsight has a very modest support for OpenGL compared to D3D.
Profiling is a very important process in software development. Dealing with multithreaded execution in a multi-core preemptive environment, that dynamically changes its performance state during execution, is quite challenging to be accurately profiled; but that is exactly what should be done with all graphics applications.
Before delving deeper into the topic, I would like to hear from you guys, what profiler are you using for developing OpenGL based applications?
Here is a short list of possible profilers:
- gDEBugger
- AMD gDEBugger - Visual Studio 2010 Extension
- AMD GPU PerfStudio 2.8
- NVIDIA Parallel Nsight
- NVIDIA Platform Analyzer (NPA)
- VSProfileLib – Very Simple Profile Library
Please broaden the list with other profilers that support OpenGL. NPA doesn't directly supports OpenGL, but it can be used for profiling GPU processes. Also, NV Parallel Nsight has a very modest support for OpenGL compared to D3D.