Syncfusion Range Bar Chart Performance Issues with 1200 Points in Blazor WebAssembly

[Ramesh S]

I am using a Syncfusion SfChart Range Bar chart that renders around 1200 data points. It performs well in a Blazor Hybrid app, but in a Blazor WebAssembly app, the performance is very poor. The chart becomes unresponsive, freezes during scrolling, and takes a long time to render. It also impacts other components on the page, such as the SfDialog loading indicator.

I prefer not to use lazy loading and want all data to be loaded at once. I have attached a Visual Studio 2026 (.NET 10) solution that includes both Blazor WebAssembly and Hybrid apps with a sample page demonstrating the issue.

Attachment: TestBlazorApp1_8f7e7eaf.zip

[Durga Gopalakrishnan]

Hi Ramesh,

Greetings from Syncfusion.

By default, when a Blazor WebAssembly application loads, the browser must first download the .NET runtime, core framework assemblies, your application DLLs, and the Syncfusion assemblies. Until all these resources are downloaded, nothing can render. After download, the WASM runtime starts, JIT compilation occurs, and then the chart is initialized.

When loading a large amount of data in a chart(that is in range bar chart, each point is rendered as a separate HTML element, so 1200 elements need to append in DOM which takes time to load), it is expected that rendering may take a few seconds in WASM because the runtime and assemblies load entirely in the browser.

To improve performance, you can enable AOT (Ahead‑of‑Time) compilation, which reduces runtime JIT work and offers faster execution in Blazor WebAssembly. We recommend publishing and hosting the application to observe the performance improvement.

  <PropertyGroup>

     //…

    <RunAOTCompilation>true</RunAOTCompilation>

  </PropertyGroup>

For more details on enabling AOT, please refer to the link below:

https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-7.0#ahead-of-time-aot-compilation

Note: Performance improvements from AOT cannot be observed in local development mode. They are visible only after publishing and hosting the application.

Please let us know if you have any concerns.

Regards,

Durga Gopalakrishnan.