Performance issues in Experience Builder with large datasets. Best practices?

GISTPFCreator

Hi everyone,

I'm currently building a data visualization app using ArcGIS Enterprise and Experience Builder. My application queries a dataset containing over 20,000 records. However, I've noticed a significant drop in performance, particularly with slow page load times and delayed chart rendering.

For context, my data is currently published as a feature layer. I have also tried publishing and consuming it as a standalone table, but I experienced the exact same performance issues in both scenarios.

Are there any effective workarounds or best practices to handle this volume of data? Specifically, I'm looking for tips on data publishing, indexing, or widget configuration that could help optimize the rendering performance in ExpB.

Any advice would be greatly appreciated. Thanks in advance!

David_McRitchie

This can be a tricky area, the first thing I would ask is how confident are we that the issue is specific to the Experience?

Something that might be useful, is using your Browser developer tools, focusing on the network tab. If we undock the window, and do a ctrl - f5 refresh on the Experience, how many requests do we see, and how long do all the requests take?

I personally aim to have my applications not take any longer than 30 seconds to load, without any user actions such as zooming or panning, and to not exceed 1400 individual requests. 

I would repeat this as well within the underlying Map Viewer and do a comparison. This will let you know if you are better trying to optimise your Experience, or if you might be better focusing on your Web Map configuration.

As with any performance considerations, you may also need to do further testing to rule out Server side, and Client side issues, such as hardware usage. For example is the Server hosting these services maxing out on CPU and Memory? If your Experience is particularly intensive, then you may also need to factor in dedicated GPU usage.

This can be a really challenging area to troubleshoot so please give me a shout if there is anything you would like more detail on. Also don't be afraid to raise a support case with your Esri software provider!

Hope that helps,

David