This is a closed issue that was originally posted on WinUI (#867). It seems more related on this repo.
In my app there are animations on two composition lights (PointLight). Somehow I notice that the effect exhausts my integrated GPU resources (nearly 100% utilization) and make the animation not fluent anymore.
The CPU model on my SB2 is i7-8650U I thought the integrated GPU is powerful enough to handle the effect but the reality proves my wrong. The cost does not directly generate by my app but dwm.exe. It seems like the effect is delegated to Desktop Window Manager to handle it.
I'm wondering is there way to optimize my implementation and reduce the cost.
Expected Behavior
A reasonable cost, 60%~80% utilization is accepted
Issue Type
[ ] Bug Report
[ ] Feature Request
[ ] Sample request
[ ] Documentation issue or request
[X] Other – Question
Current Behavior
This is a closed issue that was originally posted on WinUI (#867). It seems more related on this repo.
In my app there are animations on two composition lights (PointLight). Somehow I notice that the effect exhausts my integrated GPU resources (nearly 100% utilization) and make the animation not fluent anymore. The CPU model on my SB2 is i7-8650U I thought the integrated GPU is powerful enough to handle the effect but the reality proves my wrong. The cost does not directly generate by my app but dwm.exe. It seems like the effect is delegated to Desktop Window Manager to handle it.
I'm wondering is there way to optimize my implementation and reduce the cost.
Expected Behavior
A reasonable cost, 60%~80% utilization is accepted
Steps to Reproduce (for bugs)
MainPage.xaml <Page x:Class="Test.MainPage" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:local="using:Test" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" Background="DarkGray" mc:Ignorable="d">
MainPage.xaml.cs
Your Environment