-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Results for 2024 #6
Comments
For posterity, my results in x64 Release Mode with updated packages, on a Surface Studio 2 , and fixing the UWP test to not throw exceptions when setting StrokeDashArray
|
@JohnnyWestlake , thank you for the update. There was a time when I would have been very excited by XAML tech related benchmarks, but unfortunately, Microsoft has killed all things related to XAML for me personally. I've switched to Mac and am only looking to recoup my amortized investment in Windows these days (huge investment, sadly). I'm not surprised to see UWP still ahead. At least WinUI has pulled ahead of WPF. FYI, worked on a custom rendering engine for WPF that showed it too could outperform WinUI when leveraging a modern design for its graphics layer. In a couple months or so I plan to circle back to some of this and open up more of my private repositories to public status. Perhaps others will be able to make use of some elements. Thank you for keeping this alive. |
Interesting for me is that the .Net team have just ploughed a lot of resources into WPF, new controls, Fluent UI, etc. They've also said they're going to update to the latest DirectX versiosn :) |
I updated all packages to the latest version, for example, WinUI-2.8.6, WASDK 1.5, all run in x64 Release mode on Windows 11
( WPF ) Elapsed: 6,673 - 245 MB
( UWP ) Elapsed: 9,577 - 78 MB
( UWP ) WinUI-2.8.6 Elapsed: 9,935 - 84 MB
( WINUI) Elapsed: 12,365 - 138 MB
The text was updated successfully, but these errors were encountered: