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
Hey Martin,
I took a look at this again and I am still getting the same performance between both the Map Viewer and Classic.
I would check to see if the issues are just happening on this one WMS on your device, or if it occurs for other WMS layers.
If it is happening on numerous layers then I would recommend raising a support case with your distributor. Key things I would recommend testing are if the performance is the same on different networks as well other types of data like Hosted Feature Layers.
I would also confirm that your network/firewall follows the domain requirements from the ArcGIS Trust site.
Many thanks,
David
I can share my map to you if you send me your AGOL username and you can take a look and see the old vs new map viewer difference. It is unusable now. thanks
@David_McRitchie Anything new to share?
I have noticed that when you have more than just a handful of external Esri REST services coming into a new map viewer it will start to grind when doing anything in the interface when interacting with our hosted feature services. (symbology, filters, grouping layers, etc).
The latest project has to overlay project data over various agency & department open data sources - and no we're not going to download it all and republish 🙂
You earlier mention a limit of 10 layers - Is that an official Esri position that is documented? Link or it doesn't count. Not sure if Esri UK is the same as Esri Australia (i.e. Esri in nothing but name) and caught in the middle between users and Esri Inc. but hopeful you have something to give this thread a decent conclusion.
It has happened enough that I feel the only common denominator is AGOL - different computers, different data sources (mix of Esri REST & WxS open data services by various agencies), internet speed increasing over time but currently 100mbit only. Cannot say I can see a difference compared to when we only had 24mbit.
EDIT:
Experience Builder apps' performance are fine - users use apps but I have to make the map to publish and it is my time that is compromised.
Classic Viewer didn't fall over so it must be a new thing - Maybe I should get ADSL again, run Classic Viewer on Internet Explorer on my old XP machine? Pity that won't work with the new feature service functions and Field Maps requirements....
Also refer to https://community.esri.com/t5/arcgis-online-questions/map-viewer-is-slow-including-setting-default/t...
and the search that brought me here:
https://community.esri.com/t5/forums/searchpage/tab/message?filter=location&q=map%20viewer%20slow&lo...
Sorry I can't share a map - commercial in confidence etc. I'll see if I can find the time to build a map to share with dummy data over the government data but seeing as this is not an uncommon issue, maybe Esri could better document the exact constraints to Viewer performance rather than us trying to hunt issues blindly?
Something like - If you have a top spec PC and fast internet (100mbit+) then you should be able to load 10 external REST endpoints (examples below) + 10 organisation hosted layers.
These are typical web service sources we use A LOT :
https://spatial-gis.information.qld.gov.au/arcgis/rest/services/PlanningCadastre/LandParcelPropertyF...
Regards,
Chris
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.
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.