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 created a project with Interactive render mode "Server" and locally during development the performance was satisfactory.
I uploaded the project to IIS and when I went to access it I noticed that the performance dropped drastically. To try to solve the problem, I created a new project with Interactive render mode "Auto (Server and WebAssembly)" and created a page for the diagram in the client project where I defined @rendermode InteractiveWebAssembly. Now the diagram is being rendered without the links and I can't interact with it.
Is there any way to make it work with this render mode?
The text was updated successfully, but these errors were encountered:
Hello, did the performance drop drastically because of a ping issue or the library itself?
I have never tried this render mode, I'll do it and get back to you.
Hello! I believe it is because of ping. If I run the project on my local IIS it works fine. However, on an EC2 instance it is very slow. I thought that perhaps this can be solved by using InteractiveWebAssembly rendermode (reducing the dependency on the server for rendering and leaving the rendering of the diagram to the client). That makes sense?
Thanks!
I created a project with Interactive render mode "Server" and locally during development the performance was satisfactory.
I uploaded the project to IIS and when I went to access it I noticed that the performance dropped drastically. To try to solve the problem, I created a new project with Interactive render mode "Auto (Server and WebAssembly)" and created a page for the diagram in the client project where I defined @rendermode InteractiveWebAssembly. Now the diagram is being rendered without the links and I can't interact with it.
Is there any way to make it work with this render mode?
The text was updated successfully, but these errors were encountered: