You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I switched my application from server to client side rendering
and noticed that rendering the diagram tooks much longer now.
Do you plan to improve the performance here?
I don't want to have the extra load on top of my server for rendering
and also i don't want to use extra (blazor) signalr sockets for it.
The text was updated successfully, but these errors were encountered:
Hence, the performance delay is not specific to our control, but it is occurring for all the client side Blazor applications.
In the client side application, it is expected to have few more seconds during initial loading since it is downloading the needed resources to client browser, but it will save the back and forth communication between server and client browser once it is deployed and initialized.
Thank you for the investigation, i thought the new web assembly technology offers a much better performance. I found similar reports on the web, that the client side performance is currently bad. This issue seems to be related to the mono framework itself. Hopefully they get this fixed soon.
I switched my application from server to client side rendering
and noticed that rendering the diagram tooks much longer now.
Do you plan to improve the performance here?
I don't want to have the extra load on top of my server for rendering
and also i don't want to use extra (blazor) signalr sockets for it.
The text was updated successfully, but these errors were encountered: