-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Performance issue with ShoudRender functionality in WASM #26696
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
Comments
Thanks for contacting us. There are some definite things in this code which do not follow our perf best practices. Please follow the guidance provided and if you happen to still face performance issues let us know. |
Hi @mkArtakMSFT , We tried with Virtualize and RenderFragment for our scenarios but still, issues occur if we render more elements like 1000, 5000 and 10000 in the web-assembly sample. For Virtualize, we have created a separate issue, because we are using For Renderfragment Rendering : The lagging issue occurred if we try to render the more elements like 1000, 5000 and more. The issue will be occurred for both Server and WebAssembly sample for us. Could you please suggest for this issue? Sample file : Canvas.zip |
This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes. See our Issue Management Policies for more information. |
Task has closed automatically before we get a solution from your end. As per your Guidance, we used a RenderFragment concept but still the lagging issue occurred while using 1000 for nodes. please refer to the below attached video and modified sample file. Video link: Video Sample file : Sample In the above sample, we have rendered the node only when dragging and others are not re-rendered. Please refer to the below code example which we have used in a sample.
|
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
In order to avoid re-rendering of the child components, we have used the ShouldRender method. Even though we use this override method , we could not observe performance improvements.
To Reproduce
Index.razor is supposed to be the sample code. As child content, we have rendered 1000 counts of Node components
[Canvas.Razor]
[Node.razor]
We could not see the expected dragging performance from the above sample, although only one child component with re-render permission and the remaining child components is not permitted to re-render while mouse drag interaction.
Expected Behavior
We have allowed only one child component to re-render with each mouse move, and other Node components are not allowed to re-render. Therefore, in this case, the dragging should be smooth in performance during interaction.
Further technical details
We have hosted three samples with combinations of 1000 , 5000, 10000 elements. Sample having 5000, 10000 elements shows very performance issues.
Sample link : https://github.com/Naganathan/ShouldRenderWasm/tree/master/ShouldRenderWebAppTest
Hosted Link : https://naganathan.github.io/ShouldRenderWebAppHosted/
Replication Steps :
Note :
Could you please check the sample and hosted link and provide a suggestion to get smooth dragging of child component?
The text was updated successfully, but these errors were encountered: