topic Re: Slow loading layer in Operations Dashboard in ArcGIS Dashboards Questions

Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 15 Jul 2019 16:28:14 GMT

I added a new layer to my Operations Dashboard, and now its loading REALLY slowly- and I've had some complaints from viewers. The new layer has over 27,000 records. So I'm wondering how much is too much as far as loading data onto web apps? Or maybe the slowness has something to do with the queries I have? Any suggestions?

Re: Slow loading layer in Operations Dashboard

JohnBrockwell — Mon, 15 Jul 2019 17:00:50 GMT

Where is it coming from? SDE or hosted feature service? I'm assuming you tried to republish. Point or Polygon dataset?

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 15 Jul 2019 17:07:37 GMT

It's a point dataset, and it's a hosted feature service.

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 15 Jul 2019 17:09:57 GMT

and no, I didn't try to republish. Why would republishing the service help? ...and thanks for responding!

Re: Slow loading layer in Operations Dashboard

JohnBrockwell — Mon, 15 Jul 2019 18:38:09 GMT

27,000 point features isn't a problem. Sometimes republishing a service solves issues in ways I just can't explain. Re-publish is a common workflow to use when you can't identify the issue. Sometimes it just fixes the underlying issue.

Also, consider modifying your visible extent sometimes. I doubt anyone can make sense of 27,000 features on a single map.

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 15 Jul 2019 19:13:28 GMT

To republish- would I need to "Overwrite an Existing Service", this is what I'm thinking I would need to do- but I always get a warning message "If you overwrite this service you will lose access to the associated feature service data, including any changes that were made to the data after the service was initially published. It may affect existing clients using this service such as changing the layer order or modifying the available fields. Are you sure you want to continue?"

Re: Slow loading layer in Operations Dashboard

JohnBrockwell — Mon, 15 Jul 2019 19:33:17 GMT

Yes, that is true. Are you modifying this data? If it is just the beginning of its usage than I don't foresee any problems. Please like or mark my comments helpful. Thanks.

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 15 Jul 2019 19:41:24 GMT

Great info! Thanks John!!

Re: Slow loading layer in Operations Dashboard

JohnStowell — Tue, 16 Jul 2019 04:48:18 GMT

In case you didn't get this resolved, some other quick fixes for hosted layers that I have had success with:

- Clearing the browser cache (sometimes the issue is just on my end)

- Rebuild the spatial index (under item description > settings > rebuild indexes)

- Enable CDN / cache control if being publicly shared (under item description > settings > cache control)

Cheers, John

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Tue, 16 Jul 2019 18:40:20 GMT

Thanks John, I haven't had time to check these options out- but they sound great and I'm going to try them out. Thanks again.

Re: Slow loading layer in Operations Dashboard

מנהל_תקשובמנהל_מערכת — Fri, 02 Aug 2019 06:04:30 GMT

Hi,

I had the same problem, sometimes my dataset has over 200000 records.

I Notice there is no performance problem when my feature layer and basemap has the same projection.

I have created TPK with custom scales to fit my project needs and there are no performance issues anymore.

I think when it comes to a large number of records the projection on the flay causes the performance issues.

There a downside though, once you make your own basemap, you cant switch it to the regular arcgis online maps.

you can, however, convert your data to the Web Mercator (3857) and your problem is solved.

hope that helps you.

Iris Hadar

Re: Slow loading layer in Operations Dashboard

Chris_Anderson — Wed, 13 Nov 2019 13:47:09 GMT

Quick question, are you loading into a list? I am running into an issue where I have a dashboard that is displaying a list and details. The feature service it is pulling from has records added to daily (by hundreds to thousands during the hunting season), so the dashboard is getting slower and slower. I believe this is because Dashboard is having to load all the records into the list. All my other parts of the dashboard load quickly. This is going to be a major problem as the season continues. ESRI, please correct me if I am wrong, I think there is an enhancement in the works where the list will not load when the Dashboard is first opened. I do not know when this will be fixed. Like many other enhancements, I could really use it right now.

Chris Anderson

Florida Fish and Wildlife Conservation Commission

Re: Slow loading layer in Operations Dashboard

Babcock_Kristen_L — Mon, 18 Nov 2019 13:18:18 GMT

Hi Chris- I ended up using a web map application instead of the dashboard, and it works much better. I also needed to let folks download data and also print maps- so the web map works out better for me for those specific reasons too.

Re: Slow loading layer in Operations Dashboard

WillHughes — Wed, 22 Jul 2020 15:57:02 GMT

Seeing performance issues when querying dates in OD with a large point map service. Data is in an Enterprise GDB, and is ~ 5 mil records. Even when setting scale dependency, the dashboard is slow to update 3 indicators and 1 chart. Attribute index is on date column. When looking at the same data in the web map it is fast. The OD can take up to 30 seconds to update. Any performance tips are appreciated?

Re: Slow loading layer in Operations Dashboard

IanMackenzie — Fri, 06 Aug 2021 22:06:55 GMT

I have had load time and timing out issues that I determined were to do with how I set up my charts, a bar graph in particular. I had the maximum categories for the bar graph set to 200. I changed it to 20 and the problem was resolved. There is now the option to set an action from one widget on another so that the latter only renders when a selection is made on the former (e.g., I could set an action on a date selector so that the graph only renders once a user has selected a date range); so that functionality might help control performance issues due to rendering of graphs on large datasets.