Survey123 Online slow rendering to Web Map View layer, other AGOL layers working fine

[ToddHelt]

Is anyone else experiencing extremely slow performance when pulling point feature data from a Survey123 survey database into an AGOL Web Map, specifically as Hosted Feature Layer View filtered version of the Survey123 data? It is rendering very very slow back to the web map making the app unusable. Internet connection is good. Web map is rendering fine with all the other feature layers, its just of near-real time "live" data from the Survey123 database is choking.

We do have about 80,000 point features in the Survey123 database at this point along with 1-2 photo attachments each. The date range filter on the View layer means that we are never pulling more than about 8,000 points to be rendered at any time in that layer that is choking.

[ChristopherCounsell · Accepted solution]

No such thing as a survey123 database, unless youre using ArcGIS Enterprise? Assuming you've published to ArcGIS Online? Means your survey 123 submissions are stored as features in a hosted feature layer.

There are a bunch of things that will contribute to slow performance. 

• It's unlikely photos, as they're not called on the web map.
• By default only 2000 features display at a time from a single layer
• Adjust scale levels so they display when you zoom in.
• Disable editing
• Optimise the layer drawing
• Relative filters (e.g. 7 days before today) means it always reaches database. Never cached. Slow.
• Complex labels or symbology can slow things down.

Assuming you've published to ArcGIS online, you can disregard the survey123 component entirely, and just look at advice like the above for optimising web map performance. There's good videos and blogs.

https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/top-5-ways-to-improve-your-web-layer...

[ToddHelt · Accepted solution]

Thanks @ChristopherCounsell for your input, it was indeed a performance issue with the Survey123 hosted feature layer. I had also contacted Esri Tech Support and Dharshini Devi there had me rebuild the spatial index which I had not been doing (I know kind of a bonehead move). It took about an hour to rebuild but once completed that resolved the performance issue we were experiencing.