Scrollbar performance is often a big problem in larger WPF apps because of problems that seem trivial for small collections, but suddenly blow up with larger data sets.Also, it can be difficult in WPF to know exactly when the system is finished with an object.Instead, this is meant to be a slightly more practical guide to squeezing performance out of WPF in ways that are probably more likely affecting you.and its subclasses List Box and List View exacerbate performance problems because these controls are highly dynamic (resolution happens “late”), involve WPF collections (which are slow), and have difficult and unpredictable lifetimes for their child controls.This may not always be a practical or desirable solution, but layout passes perform faster when widths and heights do not have to be recalculated.
Finally, there are things (this, this, this, this, this, and this) that simply perform worse than you likely expect. Ideally in MVVM pattern we provide property values in our viewmodel. Mass Edit I think Controls related code should be in XAML.Although this is arguably good programming practice, it also tends to be insanely slow.If your windows/controls or your List Box Item/List View Items in a List Box/List View are coming up more slowly than you would like, it’s probably a combination of too much Resource Dictionary construction and/or Dynamic Resources. NET 4.0.) Collapse Resource Dictionaries as much as you can, and try to ensure that the contents of these dictionaries is only loaded once.
If you have a lot of binding errors, then those split seconds start to add up.