New Map Viewer is super slow to load when WMS and WMTS layers are in the map

[DougBrowning]

I have a map with 300 WMS and WMTS layers from outside my org.  I made the map in Pro and then published so that it was easy to add so many and so I could make nested groups easily.  (they are for reference by year and can vary in use a lot)

All layers are turned off.  Map Viewer classic loads them all fast no problem but of course there are no groups.

New Map Viewer totally hangs for several minutes.  Sometimes I get a memory error and other times it finally loads but its super slow to use.  I have a feeling the new map is trying to touch all the layers in some way.

Anyone know what is going on here?  Why it is touching all the layers when they are all off.

Open to any ideas.

thanks

[AnLizeGCC]

Hi,

I'm just adding a bit to that topic, as I'm experiencing as well some major performance issues trying to migrate WAB apps to EB apps, on Enterprise 11.1 though. It's on an internal instance so cannot share at the moment. I have to try on AGOL. So a bit off-topic, but similar experience.

We have a generic map (classic web map) containing around 30 layers, some of them internal, other external, some light, others with a heavy load of data. That classic map is embedded into a WAB app to expose internally our data to staff. This runs perfectly fine and extra fluid.

Converting this to a Web Map and EB app, this becomes unusable. So laggy. I tried to recreate the maps from scratch, the slowness appears at some point with heavy layers.

On a Fibre company broadband with a high spec computer, so not a hardware nor connection issue. Just poor performance from the Web Map.

I've used in the past couple of years the JavaScript API 4.x, with heavy data as well and it didn't seem to be that slow. But for some reason the new Web Map cannot keep up.

For now, we cannot migrate from WAB to EB sadly, this is clearly not good enough.

[AspenN]

We are experiencing extreme slowness in Map Viewer when compared to Map Viewer Classic since upgrading to Enterprise 11.3. The slowness gets worse and worse as the number of layers increases, regardless of layer type/source. I am writing to see if anyone has updates or has found solutions to this.

[BenBakerBSR]

@DougBrowning I am experiencing similar issues with MapViewer. However, all my data is published and self-hosted within AGOL. These maps certainly have more than 10 layers within them! Open the maps within MapViewer can take over 15 minutes but my users consuming within Experience Builder don't have any rendering / opening issues. Experience Builder has 'Lazy Loading' which works perfectly, specifying only specific layers to render. But obviously is the GIS professional who suffers when they have to edit they map within MapViewer.

@David_McRitchie Wouldn't implementing a 'Lazy Loading' equivalent within MapViewer be sensible?

Thanks

Ben

[David_McRitchie]

Hey Ben,

That is interesting to know that we can get issues on Hosted Feature Layers as well. I wasn't actually aware that Experience Builder had Lazy Loading but that is really useful to know for performance.

I'm presuming we could load a lot of these layers in Experience Builder, and not note any performance problems until we try to interact with these (perhaps through a layer list widget?). While in Map Viewer we are getting slow performance when loading the map?

Could be one to log an idea on ArcGIS Ideas. For my understanding it would be good to know what happens if we check the Datastore metrics for the Organisation?

How about if we make a new Web Map and begin loading layers in blocks? Can we identify if any specific services, or types of data are encountering the largest slow downs in data? From what I usually see in cases reprojecting on the fly can cause bad performance. Occasionally rebuilding the Spatial and Field Indexes can help a lot, particularly if data schemas are frequently changing.

Happy to discuss further,

David

[BenBakerBSR]

Hello @David_McRitchie,

Yes, you are correct - the MapViewer and layers within can be consumed easily and swiftly with the Experience Builder as I have implemented the 'Lazy Loading'. Prior to enabling the 'lazy loading' functionality the Experience Builder also struggled with loading / rendering.

Please could you provide the link for where I can publish an idea on the ArcGIS Idea website? I have browsed the ArcGIS Idea pages but cannot find where I'm able to publish an idea for myself.

I have tried adding the same layers into a new MapViewer but these still encounter the same issue.

Many thanks,

Ben

[BenBakerBSR]

Here's what the Datastore metrics look like

[RTPL_AU]

@David_McRitchie 
To give you a useful example - we often want to use the reference layers published by Queensland.
https://spatial-gis.information.qld.gov.au/arcgis/rest/services

Typically topics in transportation, biota, enviro, economy (mining stuff), planning cadastre (properties).

Maybe add some items from contours, inland waters, farming, or flood lines.
Queensland is big so an infrastructure project may span a few hundred km and nearest towns/hubs another few hundred away again.
These are all large & complex datasets hence not wanting to download & re-publish as the benefit would not be there. 
If you are mentioning  the numbers 10 & 60 as your starting points I feel Esri lost the plot a bit as a constraints map could easily exceed that. Add the project specific data and you may have 10 in a specific feature service.

yes - we do make targeted and optimised maps but sometimes you have to add a lot of info to find context between constraints & a client can turn it all on or off themselves.

What I find strange is that the published web apps seems to work fine & old map viewer (bar incompatible features) also works fine but 'New' Map Viewer sucks on a potato. 

@DougBrowning makes a good point about testing.

[L77]

I created a thread about map viewer loading very slowly, before seeing this thread. I am attaching the link to my post in case anyone has any advice. Map Viewer is basically not useable which is scary because I am trying to recreate all of the work I already did in experience builder before web app builder doesn't work anymore.

https://community.esri.com/t5/arcgis-online-questions/automatic-fallback-to-software-webgl-has-been/...

[DanLissick]

I am experiencing the same issue. Below is Esri supports response:

SummaryDocumentation:

• 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.