IntroductionEvery WPF developer knows the situation where you have a large line-of-business application, you’ve implemented all the features and when you finally run it on real data – it runs s-l-o-w.
Optimization Time!Optimization for performance is fun since a 1% change of code gets you 99% change in performance. However, finding the one location you should change can be a pain.This is why we’ve invented performance profilers. Profilers can help you pin-point the problem.
WPF?WPF applications performance problems can usually be categorized to several kinds, for example, layout related, rendering related, etc.
Following is a nice list of common places to optimize when you work with WPF applications. Microsoft provides a profiler specifically tuned for finding WPF related issues. You can find the installation guidelines on MSDN.Note: if this is the first time you use it, and you don’t get the data, try the patch mentioned in this post. When the profiler does work, it produces very interesting information.
For example, in the following image we can see the visual tree on the left and in it the hot element (painted red) where a lot of CPU cycles went (either due to rendering or layout). Read more: Arik Poznanski's Blog
Optimization Time!Optimization for performance is fun since a 1% change of code gets you 99% change in performance. However, finding the one location you should change can be a pain.This is why we’ve invented performance profilers. Profilers can help you pin-point the problem.
WPF?WPF applications performance problems can usually be categorized to several kinds, for example, layout related, rendering related, etc.
Following is a nice list of common places to optimize when you work with WPF applications. Microsoft provides a profiler specifically tuned for finding WPF related issues. You can find the installation guidelines on MSDN.Note: if this is the first time you use it, and you don’t get the data, try the patch mentioned in this post. When the profiler does work, it produces very interesting information.
For example, in the following image we can see the visual tree on the left and in it the hot element (painted red) where a lot of CPU cycles went (either due to rendering or layout). Read more: Arik Poznanski's Blog
Posts
0 comments:
Post a Comment