Extremely Slow Map Loading in ArcGIS Dashboard – Assistance Required

[mehmetaktas]

I am experiencing a significant issue with map loading in my ArcGIS Dashboard. The map data takes an unusually long time to load, causing considerable delays and impacting usability. This problem persists across multiple attempts, even when using different browsers or network connections.

Here are the details of the issue:

• Software Version: ArcGIS Enterprise 11.3
• Environment: Corporate network with Firewall (FW)
• Shared Service: Web Map
• Number of Registered Layers: 1
• Number of Records: 490,000
• Error Codes: None; the performance is extremely slow.
• Steps Taken:
  • Cleared browser cache.
  • Tried different browsers (e.g., Chrome, Firefox, Edge).
  • Ensured a stable internet connection.
• Expected Outcome: The map data should load quickly to allow for efficient use of the dashboard.

Could you please provide guidance on how to resolve this issue? Your assistance is greatly appreciated.

[KevinJohnsonSDD]

I've experienced the exact same issues the last 2 days.  My basemap will load reasonably well but the layers build extremely slowly or don't appear at all.  On 1/8/25 I was getting error messages that it could not load the layer.  I haven't opened a case with ESRI, but it appears they are having problems with content delivery.  

[Laura]

AGOL has been having issues but I see you are using Enterprise. Are your instances for the layers dedicated or shared? Sometimes changing those up or the # of dedicated instances can make a big difference. If it's shared you can try switching to dedicated and see if anything changes. 

Can also play around with the extent of the layer. Loading thousands of points far out may take a bit. 

Make sure the layer isn't publicly editable as that can also slow it down. 

[mehmetaktas]

Our instances are not dedicated; they are shared.

Regarding the extent, it is already set as I need the layer to appear this way.

As for the editability, the layer needs to remain editable since it is required for the data and graphics I have prepared.

[RyanUthoff]

Does the map load slow if you directly view the map in the map viewer (outside of the dashboard)? Or is it slow only when accessing it through the dashboard?

[mehmetaktas]

The map loads slowly in both cases, whether I access it directly in the Map Viewer or through the dashboard.

[RyanUthoff]

Do you have other maps containing data from other feature services and databases in Portal? And if so, are they going slow as well?

Basically, what you will need to do is isolate the problem. Either narrow it down to a specific feature service or a specific component of ArcGIS Enterprise environment.

If the issue is isolated to only this one feature service, then it's possible that there is something wrong with the underlying data. Such as spatial/attribute indexes needing to be reindexed. 

If everything is slow, then it could be a problem with your enterprise environment. Perhaps security software is slowing it down, or something is misconfigured elsewhere. In that case, you'd probably need to work with your IT department to troubleshoot that further.

[mehmetaktas]

Yes, there are other map services in the Portal, and they are also slow. I have already created indexes for the geometries in the data, but it did not make any difference. I have also consulted with the IT department in our organization, and there does not appear to be any issues caused by security software blocking or interfering.

[DanLissick]

I am seeing the same thing for the new map viewer being slow. Below is Esri support's response:

Summary/Documentation:

• The information we received from internal is that this behavior is expected with 4x (i.e., the Maps SDK for JavaScript). Complex polyline and polygon layers are generalized to improve query time. This is different than 3x which loads these geometries differently.
• We also see layers be generalized/optimized by default when they have more than 400,000 vertices to protect the organization's datastore. This is mentioned in our documentation here:
  •  Manage hosted feature layers—ArcGIS Online Help | Documentation.
• From the example layer with which we've reproduced the behavior with in-house, we observed that it's a complex polyline layer that by default, has been optimized by the software upon publishing.
• In general, we have the mantra of no more than one vertex per pixel at any particular scale, meaning that data is being generalized dynamically when being viewed. This isn't bluntly stated in our documentation anywhere, but this topic is touched on in the video resource linked below. Note the discussion at about 24:50 minutes in.
  • Optimize ArcGIS Online Maps and Apps for Audiences of Any Size - Esri Videos: GIS, Events, ArcGIS Pr... 
• This blog also touches on a similar topic of discussion:
  • Essential Configurations for Scalable ArcGIS Online Web Applications.
• My colleague that I was working with has mentioned to internal that the difference between 3x and 4x loading should be documented somewhere - but they would also encourage you to leave feedback directly on our documentation using the 'feedback on this topic?' option on the Map Viewer documentation page as well.
• Additionally, the reason that ArcGIS Field Maps and our other Mobile applications do not display the same behavior is because our mobile apps are not built on the same code base - JavaScript is used for web clients while our mobile apps use a product called ArcGIS Runtime or ArcGIS Maps SDKs for Native Apps | Documentation | Esri Developer.
• The existing Enhancement requesting an improvement in how Map Viewer renders features upon zoom in is ENH-000163087, and has been attached to this case.

I've also provided the feedback you passed along to me in regards to this change and inquired regarding if escalating an Enhancement is possible.

Unfortunately there isn't a set process of escalating an Enhancement in the same way that bugs can be escalated - Our bug escalation documentation page states this directly. However some indirect methods of escalating it would include creating a post on our ArcGIS Ideas forum, which can bring additional views and attention to the issue as our development team does browse the ArcGIS Ideas forum. If you do end up doing this, if you can provide me with the link to the Ideas Page, I can directly attach it to the Enhancement to route other users that create cases for this issue to the same enhancement number.