How to profile a WPF application?

Patrick

I try to figure out what is slow in my test application but the method listings show that the majority of time is spend in low-level methods such as

MS.Win32.NativeMethods+WndProc.Invoke(...)

The slowest method with Source code is only shown as 3.5 % time with children. I just don't know how to read this.

Are there tutorials on how to profile a WPF application? What does the 3.5% mean?

Patrick

Also, when I go into the grid method view it shows that AppMain.StartApplication() and AppMain(string[] args) take 49.6% time with children and the next real method only 3.68 ... what does that mean?

Brian Donahue

Hi Patrick,

Profiling a WPF application is exactly the same as any other type of application.

I'd recommend changing the results from "wall clock" time to "CPU time" as your application's entry point (main) will always show the full length of time that you were profiling the applicaiton under wall-clock time.

Maybe the CPU time can further rationalize the rest of your results as well.