Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

With the chart control, when you apply a zoom you can enable a scrollbar. I'm finding when running with the component on 'InteractiveServer' the scrolling is smooth, but in WebAssebly mode it's veryjerky and choppy, and causes quite high cpu usage on an i7 laptop. It's slightly improved when going from debug to release mode with AOT, but still noticeably choppy enough for the stakeholders who are reviewing my app to complain.

In performance profiler, I can see that the syncfusion-blazor js is doing quite a lot of granular wasm interop which is where this cpu load is coming from:


Empty


It looks like there's a  lot of JS interop happening when tracking mouse move.

Rapid/granular js interop can really hurt performance as outlined below:

Interop avoid fine grained calls

Interop and onmousemove

 

Can this be reviewed for enhancement? Perhaps per Microsoft's examples above the interop calls can be consolidated or rate limited, or perhaps eliminated completely by using Blazor native code to handle mousemove:



I've attached a sample project where you can try this out, have a look at 'ChartDataHost' in the Client project, and experiment between InteractiveWebAssembly and InteractiveServer