-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Slow Collectionview Rendering performance in Maui compared to Xamarin #24224
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
This issue has been verified using Visual Studio 17.11.0 Preview 7.0 (8.0.80 & 8.0.40 & 8.0.3 & 7.0.101). Can repro on iOS and Android platforms. |
Any updates on this? |
Hi .NET MAUI team, we are also encountering the same issue on android platform. Could you please provide an update on the status of this issue and an estimated timeline for a fix? Thank you for the support. Regards,, |
For cross referencing I believe I have found one of the causes (if not the main cause) of the poor performance in scrolling/translation in iOS Maui. Every time you change the translation of any objects in iOS, Maui is causing the whole hierarchy to re-arrange itself and re-measure itself in iOS. This is not happening in Android/Windows. I have shared my bug report here which demonstrates the issue: #24996 |
Important observation: |
Added Speedscope file to isolate navigation to Collection View 2 page. https://github.com/brentpbc/maui-xam-testing/blob/2ab538c0ed68c6170d7558be4370f35bb4988bee/CollectionViewTesting1/Speedscope/iPad_6gen_sim_CollectionViewTestAppMaui_Nav_cv2.speedscope.speedscope.json |
Description
I am currently migrating our existing LOB app that is on the iOS app store from Xamarin Forms to .Net Maui and I am noticing performance issues in the Maui version compared to the Xamarin version. This is most noticeable when testing on older slower devices such as the 2018 6gen iPad we have access to which is a good representation of the devices our customers would be using.
I have created an example repo https://github.com/brentpbc/maui-xam-testing.git that contains a Xamarin solution and a Maui solution, both have essentially the same code. In the test app there is a "CollectionView2 Page" button, in the Maui version after tapping the button there is a delay navigating to the "CollectionView2 Page" which is not present in the Xamarin version and then once the page is displayed the scroll stutters and doesn't match the performance of the Xamarin version. Both versions were built in Release mode when comparing. See below screen recordings for a comparison.
Xamarin solution: https://github.com/brentpbc/maui-xam-testing/tree/main/CollectionViewTesting1/CollectionViewTestAppXam
Maui solution: https://github.com/brentpbc/maui-xam-testing/tree/main/CollectionViewTesting1/CollectionViewTestAppMAUI
MAUI ios Simulator iPad 6Gen Speedscope File: https://github.com/brentpbc/maui-xam-testing/blob/main/CollectionViewTesting1/Speedscope/iPad_6gen_sim_CollectionViewTestAppMAUI.speedscope.json
Xamarin Screen Recording:
https://github.com/brentpbc/maui-xam-testing/raw/main/CollectionViewTesting1/ScreenRecordings/iPad_6gen_device_Xamarin.mp4
iPad_7_Xamarin.mp4
Maui Screen Recording:
https://github.com/brentpbc/maui-xam-testing/raw/main/CollectionViewTesting1/ScreenRecordings/iPad_6gen_device_Maui.mp4
iPad_7_Maui.mp4
Steps to Reproduce
Link to public reproduction project repository
https://github.com/brentpbc/maui-xam-testing.git
Version with bug
8.0.80 SR8
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
iOS, Android
Affected platform versions
No response
Did you find any workaround?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: