Geek Answers Handbook

Can't I fully understand how to use the Visual Studio 2008 profiler?

complaints {

I always end up incredibly disappointed when I switch to the profile of my code using the Visual Studio 2008 profiler (from the Analysis menu option). This is one of the poorest VS designs, in my opinion, and I cringe every time I need to use it.

}

I have a few questions regarding use, I hope you guys can give me some pointers :-)

  • Do you need your projects embedded in Debug or Release to profile them? One dialogue (which I do not know how to return about) mentioned that I should profile in the Release section. Ok - I do this - when I go to run the code, it tells me that I do not have enough PDB files. Awesome. So I return to Debug mode and I try to run it, and it tells me that half of my projects need to be recompiled with / PROFILE enabled.
  • Is it possible to profile projects in C ++ / CLI? When the / PROFILE switch is on, half the time I get absolutely no results from my C ++ / CLI projects.
  • Why when trying to profile projects in C # they appear in the report in the "View modules" section? List of names like 0x0000001, 0x0000002, 0x0000003, etc.? Really, VS? Indeed? Can't you guess the names of my modules?
  • In this case, the function names are called 0x0A000011, 0x06000009, 0xA0000068, etc.
  • Why, and why, does VS rebuild EVERYTHING in the dependency tree of the executable? This may not be a problem if you have 5-6 projects in your solution, but when you have 70 , it is almost faster than not even bothering the profiler .
  • Can you recommend any good guides on using the VS2008 profiler?
+4
source share
4 answers

1. Do you need your projects to be built in Debug or Release to profile them?

Usually you use Release mode.

6. Can you recommend any good guides on using the VS2008 profiler?

Step 1, download ANTI Profiler .

Step 2, follow the simple instructions on the screen.

Step 3, see easy-to-read reports.

Seriously, Microsoft's profiler is rubbish compared to ANTS.

+1
source

If you find it difficult to use, there is a really great .NET profiler called nprof , and if you're debugging projects other than the CLR, AMD has a really impressive statistical profiler called Code Analyst .

Both are free (!) And extremely easy to use. This is a much more pleasant alternative, and I expect from your post above that you are ready to disrupt the VS profiler anyway :)

+3
source

I have the same feeling. I ended up writing my own (all I need is great info about the time the method was called).

+1
source

Just a general comment. There are several reasons for people.

  • To get a variety of time information.
  • To find out what they can fix to speed up their program.

These are different goals.

If your reason is second, using a profiler is not the only way. Look here

+1
source

More articles:


All Articles