"Microsoft claims to have achieved a "leap forward" in performance for WinUI 3, the current native framework for Windows apps, with a 25 percent improvement for the parts of File Explorer coded using this framework. Software engineer lead Beth Pan posted figures for the WinUI portion of File Explorer, showing 41 percent fewer memory allocations and 45 percent fewer function calls."
"She added that some optimizations "involve small or large breaking changes," so they will be opt-in at first for developers using the framework. The plan is for the optimizations to become the default in future versions of WinUI and the Windows App SDK, with opt-out available when needed."
"The new optimizations are part of a push to make Windows more responsive. In March, Windows boss Pavan Davuluri promised to improve the quality of the operating system, including a commitment to a "faster and more dependable File Explorer." His post noted that Microsoft intends to "move more experiences to WinUI 3" for faster responsiveness."
"Performance issues with WinUI 3 have been well known for years. Although Microsoft calls it a native framework, that is a stretch. WinUI 3 is based on WinRT (Windows Runtime), a component interface first used in Windows 8 that sits between application code and the underlying Win32 API, which has a better claim to being native."
Microsoft reports a 25% performance improvement in WinUI 3 code used in File Explorer. Reported results include 41% fewer memory allocations and 45% fewer function calls for the WinUI portion. Some optimizations require small or large breaking changes, so they will be opt-in initially for developers using WinUI and the Windows App SDK. The optimizations are intended to become the default in future versions, with opt-out options when necessary. The work supports a broader effort to make Windows more responsive, including moving more experiences to WinUI 3. Developers have previously reported that WinUI 3 is measurably slower than WPF and UWP, and that it cannot be considered smooth while using WinUI 3.
Read at theregister
Unable to calculate read time
Collection
[
|
...
]