Performance Issue in WPF
-
I have WPF application that performs scrolling of three xaml controls in circular manner. If I use simple control without much styles or instead use a simple image in the element, then scrolling goes fine and application performance is good. However, if I load the control with heavy WPF styles,then at very high resolution say (1400 * 900) systems, scrolling gets jerky and CPU usage increases.The problem exists with machines with low graphic card. I studied this and found that WPF can take advantage of hardware rendering pipeline but couldn't find any working example. Is there some way in WPF by which we can use heavy styled xaml controls with good performance on PCs with UMA graphic card?
-
I have WPF application that performs scrolling of three xaml controls in circular manner. If I use simple control without much styles or instead use a simple image in the element, then scrolling goes fine and application performance is good. However, if I load the control with heavy WPF styles,then at very high resolution say (1400 * 900) systems, scrolling gets jerky and CPU usage increases.The problem exists with machines with low graphic card. I studied this and found that WPF can take advantage of hardware rendering pipeline but couldn't find any working example. Is there some way in WPF by which we can use heavy styled xaml controls with good performance on PCs with UMA graphic card?
Why do you think you are going to get an answer to the one I gave below? Didn't you believe me? Did you somehow think that I was pulling this information out of my a*se just to yank your chain? You've been told the solution. Now actually get off your a*se and do something about it.:mad:
Deja View - the feeling that you've seen this post before.
-
Why do you think you are going to get an answer to the one I gave below? Didn't you believe me? Did you somehow think that I was pulling this information out of my a*se just to yank your chain? You've been told the solution. Now actually get off your a*se and do something about it.:mad:
Deja View - the feeling that you've seen this post before.
Pete's right ... WPF unlike winforms uses the graphics engine of the machine to 'paint' screens. This is all done throuh the MILCORE and DirectX ... "The major components of WPF are illustrated in the figure below. The red sections of the diagram (PresentationFramework, PresentationCore, and milcore) are the major code portions of WPF. Of these, only one is an unmanaged component – milcore. Milcore is written in unmanaged code in order to enable tight integration with DirectX. All display in WPF is done through the DirectX engine, allowing for efficient hardware and software rendering. WPF also required fine control over memory and execution. The composition engine in milcore is extremely performance sensitive, and required giving up many advantages of the CLR to gain performance." Get a better machine ... To be fair WPF is arguably very 'Vista' related meaning that you should really say to users that minimum specs of machine are more ot less what you would expect in order to run Vista. That is certainly what we are going to be doing when we roll out our new software ...
Jammer Going where everyone here has gone before! :) My Blog
-
Pete's right ... WPF unlike winforms uses the graphics engine of the machine to 'paint' screens. This is all done throuh the MILCORE and DirectX ... "The major components of WPF are illustrated in the figure below. The red sections of the diagram (PresentationFramework, PresentationCore, and milcore) are the major code portions of WPF. Of these, only one is an unmanaged component – milcore. Milcore is written in unmanaged code in order to enable tight integration with DirectX. All display in WPF is done through the DirectX engine, allowing for efficient hardware and software rendering. WPF also required fine control over memory and execution. The composition engine in milcore is extremely performance sensitive, and required giving up many advantages of the CLR to gain performance." Get a better machine ... To be fair WPF is arguably very 'Vista' related meaning that you should really say to users that minimum specs of machine are more ot less what you would expect in order to run Vista. That is certainly what we are going to be doing when we roll out our new software ...
Jammer Going where everyone here has gone before! :) My Blog
-
Thanks for the reply. I have already lowered the Bitmap effect and applied the caching still in need more performance, can you suggest something ? Can i somehow further reduce the rendering quality while doing doing some particular task? Thanks
Since WFP is practically DirectX it might be worth investigating down this route ... Maybe experiment with you images as well. I can't imagine a scenario where I would want to degrade quality though so i've never looked into this.
Jammer Going where everyone here has gone before! :) My Blog