This may be a simple yes/no answer, but I'm looking for input as I just started using Experience Builder.
I've got a web map consisting of a hosted feature layer and a feature service displayed in my un-published Experience Builder. I've created multiple data views of layers within the feature service inside of Experience Builder.
Since doing so, we've experienced slowness on our GIS servers and some serious CPU usage. The timing of the slowness and the work done in Experience Builder does seem to match up, but with the Experience Builder being unpublished and nobody using it, I'm hesitant to delete the Data Views and lose the work that I've done.
Has anyone else experienced slowness after using a feature service and data views within Experience Builder?
Thanks in advance for any input and advice!
Yes, I have run into performance issues with hosted, views.
My issue is specifically with the featureinfo widget, although I also see performance issues with just loading the view.
Here is the link to the post I just created on my issue.
Hi @JoshSmithWCWD , @KGalluccio ,
The performance issue could be caused by many reasons. Could you please provide a sample app so that we can debug and figure out the causes?
Thanks,
Dan