digram blazor wasm project is slow

digram blazor wasm project is slow, even with single node drag is slow. is diagram blazor wasm project is recommended or blazor server app is recommended


1 Reply

BR Balavignesh RaviChandran Syncfusion Team February 3, 2025 08:38 AM UTC

Hi Krishna Kishore,

We recommend using Blazor WebAssembly (WASM) for your application. Here’s why:

  • Faster Interactions: Once the app is loaded, actions like dragging nodes are faster because they happen directly in the user's browser, without needing to contact the server.
  • Less Server Load: With WASM, the server doesn’t have to handle every user interaction, which can make the app more efficient.

Important Points:

  • Initial Load Time: WASM apps can take longer to load initially since they need to download more data to the browser. However, after that, the app runs more smoothly.
  • Blazor Server: While it loads quickly at the start since it doesn’t download as much data, every interaction (like dragging a node) involves communicating with the server, which can make things slower.

Below we share a comparison of the performance metrics observed when dragging a single node in both application types:

Performance Overview:

Interaction

Time taken in Server

Time Taken in WASM

Single Drag

763ms

472ms

Multiple drag(3 times )

1957ms

1497ms

Multiple drag(5 times )

2370ms

1940ms


Overall, if you want better performance while interacting with the app, especially for tasks like dragging a node, we suggest using Blazor WASM. If a quick initial load is more important and you can handle slightly slower interactions, Blazor Server might work for you.


Loader.
Up arrow icon