Infinite animation causes high CPU usage

[stevemonaco]

Forgot to report for tracking. This is the only animation in the app and the effect is pretty subtle.

Solitaire/Solitaire/Styles/TrayContainer.axaml

Lines 51 to 67 in 8f5a371

	<ControlTheme.Animations>
	<Animation Duration="0:1:0" IterationCount="Infinite" PlaybackDirection="Alternate">
	<KeyFrame Cue="0%">
	<Setter Property="BorderBrush">
	<LinearGradientBrush StartPoint="-1000,1000" EndPoint="1000,0"
	GradientStops="{StaticResource GoldBrush}"
	Transform="rotate(120deg)" />
	</Setter>
	</KeyFrame>
	<KeyFrame Cue="100%">
	<Setter Property="BorderBrush">
	<LinearGradientBrush StartPoint="-2000,1000" EndPoint="0,-1000"
	GradientStops="{StaticResource GoldBrush}" />
	</Setter>
	</KeyFrame>
	</Animation>
	</ControlTheme.Animations>

[maxkatz6]

From the discussion on the telegram, does it seem like this animation actually improves general smoothness of the app? By forcing render each frame.

[stevemonaco]

I can't really tell any smoothness difference here during intense animation (dealing). The Solitaire app itself doesn't have much in the form of interactive UI elements (eg. even the buttons don't have :pointerover effects) so there isn't anything that needs to quickly wake up.

This is with package updates to 11.3.0-beta2, publish -c Release + dotnet serve, and on a 60fps display using Edge (Windows).

[maxkatz6]

It might be multithreading specific problem

[stevemonaco]

I'm working on my own MT WASM app and came across this again. Single thread worked fine, MT would pause about a full second before a pointerover color change started.

Instead of using an infinite animation, I seem to be able to fix it with:

var options = new BrowserPlatformOptions()
{
    PreferManagedThreadDispatcher = false
};