How should I profile visual c++ express?

Question

I\'ve read a lot of the posts here giving profiling advice but I need to ask this.

From what I can tell, Visual C++ Express doesn\'t generate a debugging file that i

Answer 1

It isn't hard to write your own profiler. Or you could pick up an open source that has some testing behind it. You might want to look at my own open source profiler, called cRunWatch

Answer 2

Are you sure? IIRC, Visual Studio Express can create the .PDB file, though you might have to ask it to generate debugging information for you if you are using a release build. (It has to -- otherwise Visual Studio's debugger wouldn't work!)

Answer 3

First, the polar angular velocity of the car should be proportional to the speed of the car and to the angular position of the steering wheel (to a first approximation).

Second, there's hardly a professor or blogger or book author who will tell you this, but if you want to see what the code is doing and optimize it, the hands-down simplest way is this.

Added: Programmers have a strong tendency to assume that any automated profiling tool will do a better job than the manual technique, but that depends on the details of exactly what they do. Most of them implement what's popular rather than what is most effective. The result is some performance problems being missed, putting a cap on the speedup you can get. Here is a list of common misconceptions that result in failing to find performance problems.

Some profilers do get it nearly right, including RotateRight/Zoom and LTProf.