Sunday, August 17, 2008
Code profiling tools
I've spent a few hours looking for good code profiler for my game engine, optimally if it could be integrated into Visual Studio 2005. So here is my report, hopefully it will save time to somebody.
There are some payed profilers:
- Intel's VTune
- Compuware's DevPartner Performance Analysis
- Visual Studio Team Edition has integrated profiler (my professional edition doesnt).
Then some free:
- IProf, which seems to need to add some lines into every function that should be profiled, which is very nonpractical
- gprof for gcc (not for VS)
Some tools are also listed on wikipedia: List_of_performance_analysis_tools.
And finally the profiler of my choice.
AMD's CodeAnalyst is for free, is integrated into VS2005, and works very well. It works on Intel processors too, only some HW-related features are unavailable. To download CodeAnalyst, registration is required - that's where bugmenot.com helps. By the way, in order to get proper results, project should be compiled as release, with debugging information used (Program Database /Zi).
So, my first post. I hope posts will stay this informational in future.
There are some payed profilers:
- Intel's VTune
- Compuware's DevPartner Performance Analysis
- Visual Studio Team Edition has integrated profiler (my professional edition doesnt).
Then some free:
- IProf, which seems to need to add some lines into every function that should be profiled, which is very nonpractical
- gprof for gcc (not for VS)
Some tools are also listed on wikipedia: List_of_performance_analysis_tools.
And finally the profiler of my choice.
AMD's CodeAnalyst is for free, is integrated into VS2005, and works very well. It works on Intel processors too, only some HW-related features are unavailable. To download CodeAnalyst, registration is required - that's where bugmenot.com helps. By the way, in order to get proper results, project should be compiled as release, with debugging information used (Program Database /Zi).
So, my first post. I hope posts will stay this informational in future.
Labels: programming
Subscribe to Posts [Atom]