| title | description | ms.date | dev_langs | helpviewer_keywords | ms.assetid | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Optimizing Performance: Other Recommendations |
Learn how to optimize the performance of your applications with this list that is more expansive than the basic application performance overview. |
03/30/2017 |
|
|
d028cc65-7e97-4a4f-9859-929734eaf40d |
This topic provides performance recommendations in addition to the ones covered by the topics in the Optimizing WPF Application Performance section.
This topic contains the following sections:
When you use a xref:System.Windows.Media.Brush to set the xref:System.Windows.Shapes.Shape.Fill%2A or xref:System.Windows.Shapes.Shape.Stroke%2A of an element, it is better to set the xref:System.Windows.Media.Brush.Opacity%2A?displayProperty=nameWithType value rather than the setting the element's xref:System.Windows.UIElement.Opacity%2A property. Modifying an element's xref:System.Windows.UIElement.Opacity%2A property can cause WPF to create a temporary surface.
The xref:System.Windows.Navigation.NavigationWindow object derives from xref:System.Windows.Window and extends it with content navigation support, primarily by aggregating xref:System.Windows.Navigation.NavigationService and the journal. You can update the client area of xref:System.Windows.Navigation.NavigationWindow by specifying either a uniform resource identifier (URI) or an object. The following sample shows both methods:
[!code-csharpPerformance#PerformanceSnippet14] [!code-vbPerformance#PerformanceSnippet14]
Each xref:System.Windows.Navigation.NavigationWindow object has a journal that records the user's navigation history in that window. One of the purposes of the journal is to allow users to retrace their steps.
When you navigate using a uniform resource identifier (URI), the journal stores only the uniform resource identifier (URI) reference. This means that each time you revisit the page, it is dynamically reconstructed, which may be time consuming depending on the complexity of the page. In this case, the journal storage cost is low, but the time to reconstitute the page is potentially high.
When you navigate using an object, the journal stores the entire visual tree of the object. This means that each time you revisit the page, it renders immediately without having to be reconstructed. In this case, the journal storage cost is high, but the time to reconstitute the page is low.
When you use the xref:System.Windows.Navigation.NavigationWindow object, you will need to keep in mind how the journaling support impacts your application's performance. For more information, see Navigation Overview.
Hit testing on large 3D surfaces is a very performance intensive operation in terms of CPU consumption. This is especially true when the 3D surface is animating. If you do not require hit testing on these surfaces, then disable hit testing. Objects that are derived from xref:System.Windows.UIElement can disable hit testing by setting the xref:System.Windows.UIElement.IsHitTestVisible%2A property to false.
The xref:System.Windows.Media.CompositionTarget.Rendering?displayProperty=nameWithType event causes WPF to continuously animate. If you use this event, detach it at every opportunity.
Whenever possible, avoid using the xref:System.Windows.Controls.ScrollBarVisibility.Auto?displayProperty=nameWithType value for the HorizontalScrollBarVisibility and VerticalScrollBarVisibility properties. These properties are defined for xref:System.Windows.Controls.RichTextBox, xref:System.Windows.Controls.ScrollViewer, and xref:System.Windows.Controls.TextBox objects, and as an attached property for the xref:System.Windows.Controls.ListBox object. Instead, set xref:System.Windows.Controls.ScrollBarVisibility to xref:System.Windows.Controls.ScrollBarVisibility.Disabled, xref:System.Windows.Controls.ScrollBarVisibility.Hidden, or xref:System.Windows.Controls.ScrollBarVisibility.Visible.
The xref:System.Windows.Controls.ScrollBarVisibility.Auto value is intended for cases when space is limited and scrollbars should only be displayed when necessary. For example, it may be useful to use this xref:System.Windows.Controls.ScrollBarVisibility value with a xref:System.Windows.Controls.ListBox of 30 items as opposed to a xref:System.Windows.Controls.TextBox with hundreds of lines of text.
The WPF Font Cache service shares font data between WPF applications. The first WPF application you run starts this service if the service is not already running. If you are using Windows Vista, you can set the "Windows Presentation Foundation (WPF) Font Cache 3.0.0.0" service from "Manual" (the default) to "Automatic (Delayed Start)" to reduce the initial start-up time of WPF applications.