topic Re: Map Viewer is slow, including setting default visualization in ArcGIS Online Questions

Map Viewer is slow, including setting default visualization

AlfredBaldenweck — Fri, 01 Jul 2022 20:34:37 GMT

Does anyone have any suggestions for making new Map viewer not be so slow?

This seems to be a recurring issue. I like a lot of Map Viewer's functionality, but I really am having a hard time waiting for it to do anything.

It is painful to try to make any changes to a map, such as filtering or changing symbology. Forget editing. I understand it on maps with a bunch of stuff, but it's even affecting setting visualization for feature classes on their own item page. I just set symbology for an empty feature class and it took forever to load. I do not mean the map, I mean each menu when you click on it or make any changes.

I'm also confused because all of the applications that use the maps don't seem to have any slowness? Collector/FieldMaps has no problem, for example. Just Map Viewer seems to be slow.

If anyone has any tips for making it not so slow, I'd appreciate it. Thanks!

Re: Map Viewer is slow, including setting default visualization

CMV_Erik — Fri, 01 Jul 2022 23:09:55 GMT

No suggestions, but we have been troubleshooting the same problem with Esri support team. We have started suggesting people use Field Maps as a workaround.

Re: Map Viewer is slow, including setting default visualization

AlfredBaldenweck — Sat, 02 Jul 2022 08:11:13 GMT

That’s part of the issue; I’m trying to configure things for use in FieldMaps and it’s just taking forever.

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Sat, 02 Jul 2022 12:31:46 GMT

Can you share the map and we can take a look?

Re: Map Viewer is slow, including setting default visualization

AlfredBaldenweck — Thu, 07 Jul 2022 19:49:46 GMT

Hi Russell,

I don't have a map that's shareable right now, but I did some testing. To be honest, this issue might just be a limitation of the tech.

Another thing I'm unsure of is if Map Viewer runs better on some browsers or not, and how much that might be causing my issues.

I'm using Edge (I know) since that's what we use at work, but if it runs better on other browsers, I'd appreciate knowing about it. Maybe this would all get better if I just switched to Chrome or Firefox or something.

I'm spoilering the timing that I think is just par for the course. I'm not sure how much can actually be changed.

In particular, opening the properties tab tends to take a while. To be fair, only 4-6 seconds, and since it is a synthesis of the other tabs, I think that's annoying but fair.
Opening the map takes typically around 30 seconds before I can actually open menus. Testing on a feature class's visualization page (about 6 records) took about 25 seconds, while opening a map with plenty of layers took about 40 seconds. Given the huge number of records in the actual map, this discrepancy makes sense.
Opening the other menus typically is a 2-3 seconds, although things like pop-ups and symbology tend to take longer, even if no expressions are used.
Filtering is generally kind of slow, both in un/applying the filters and editing them, taking several seconds to filter about 20 records down to one, using one clause.

Zooming tends to lag. Again, to be expected with lots of records to redraw.

These are the two things that I think can be changed.

Opening up the Arcade editor takes a while, often longer than 7 seconds.
There is significant lag while trying to click on another menu while one is open or opening.
- Given the several seconds it frequently takes to open a menu, misclicking and trying to correct the click can take a long time; you're not really sure what you've clicked and it isn't responsive enough for you to know when to stop clicking.
- This also includes just running the mouse down the side to highlight each menu's button.
Adding and removing Layers takes a long time.

I do want to reiterate that I do understand that sometimes things just take a while to happen. There's a lot of stuff going on in Map Viewer, especially when you have several different layers all doing different things. When it works, it works great. My complaint is just how long it takes to get there.

Thanks

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Thu, 07 Jul 2022 19:57:36 GMT

Yup definitely will need a copy of the map to help assist looking into it. If you can pop the map and layers into a group and invite russell_jsapi to that group and I can take a look.

how many layers in the map are you using? What types of layers are you using?

Are you using edge or edge(chromium)?

Re: Map Viewer is slow, including setting default visualization

Ole_MariusGulbrandsen — Wed, 14 Dec 2022 09:43:01 GMT

We also have the same problem with the new map viewer 🙄 Everything seems to work fine in the old map viewer and/or web app builder. We started to use the new map viewer and experience builder because we wanted to group layers and make use of all the new widgets in EB. Now all of our bigger project running on the new map viewer and in Experience builder are so slow. I do not want to convert back to the old map viewer and webappbuilder, because we really like and find the new funcionalities in EB and new map viewer very useful.

Link to two of our road project running on EB and new map viewer:

Old project.

https://experience.arcgis.com/experience/3c016ede34fc4936a91bd33c17f3b5c1

New project:

https://experience.arcgis.com/experience/4f40ac3daaad4eb197c39189b53052e5

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Wed, 14 Dec 2022 14:10:37 GMT

Are you seeing Map Viewer behaving slow or Experience Builder? I checked the load times for the maps in Map Viewer and was seeing 3.5-4 seconds with both maps from the 2 different experience builder links. Map Viewer Classic was showing roughly 4-4.5 seconds for me.

Re: Map Viewer is slow, including setting default visualization

Ole_MariusGulbrandsen — Wed, 14 Dec 2022 14:24:09 GMT

Both, Experience Builder and the new map viewer are slow in mye opinion. Turning on and off sublayers, using the draw and print widgets. Working with the symbology, labels etc on the map layers, moving around in the map and more. For me this works so much quicker in the old web map and web app builder unfortunately.

Link to both of the projects web maps:

E18_TB_2D_kart (arcgis.com)

E18_Gjerstad_Bamble (arcgis.com)

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Wed, 14 Dec 2022 14:38:06 GMT

Can you provide some more detail

Turning on/off layers and draw + print widgets - Is this experience builder only?
What are doing and seeing with working with symbology, labels etc that is different vs. Map Viewer Classic?

thank!

Re: Map Viewer is slow, including setting default visualization

Ole_MariusGulbrandsen — Wed, 14 Dec 2022 14:47:09 GMT

The widgets in experience builder are not that important but I suspect that the 2D map is the issue here. EB works fine if I build in a 3D scene. When I turn back to the 2D map everything things go a lot slower.

If I want to change the colors on map object, adjust transparency or something like that the map responds very slow.

Re: Map Viewer is slow, including setting default visualization

AlfredBaldenweck — Wed, 14 Dec 2022 14:47:21 GMT

Thank you to @Ole_MariusGulbrandsen for poking this thread.

I'm using Edge (Chromium).

Layers vary. My project map has upwards of 30, but again, this lag also appears on the visualization tab of individual item pages. It makes sense to lag with 30 layers. It doesn't for one.

It's also worth pointing out (and most frustrating), that this lag occurs (on the Visualization tab), in layers with ZERO records. Seriously, make a new feature class, any number of fields, and before you populate any records, try setting a default visualization. It is sloooow, which is baffling because there's nothing for it to render.

I unfortunately do not have any maps that I can share other than just creating an empty feature class to play with.

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Wed, 14 Dec 2022 15:06:55 GMT

Can you point to some of the layers you are making those changes just so I am reproing something close to what you are doing. Thanks!

Re: Map Viewer is slow, including setting default visualization

AndersAstad — Wed, 01 Mar 2023 11:56:24 GMT

I am also experiencing abysmal performance in the new map viewer in projects with a lot of layers. There is a lot of stuttering, and general slowness while moving around in the map and opening a layer's properties.

One thing I have figured out is that the performance is at its worst when I am in the "Layers" panel. If I go to for example "Basemaps" the stuttering clears up and everything is a lot more responsive.

The performance issue transferes to experience builder app (https://experience.arcgis.com/experience/157c166b18e849a6aaa8606882d19453/page/Page/). This is a copy of a WAB app, where grouping if layers is a much needed feature as there are a bunch of layers. The performance in the WAB is very acceptable, however the performance in the EB version is not as good.

I have tried editing and viewing in Edge, Chrome, and Firefox. Poor performance in all three browsers.

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Wed, 01 Mar 2023 14:30:12 GMT

Thanks for sending over an example. Both Map Viewer and Experience Builder use the same API for the map view and would have similar experience.

Re: Map Viewer is slow, including setting default visualization

HighlandCouncil — Tue, 04 Apr 2023 14:02:40 GMT

There's definitely a performance issue with the new map viewer and experience builder. I first tried to use them a couple of years ago and they were both so slow that I gave up and returned to classic map viewer and web app builder. I've recently tried the new map viewer/experience builder again and performance is still terrible. This is even just creating a new map and adding a single layer - it's very much slower than classic map viewer.

I've tried loading the maps linked to earlier in this thread by:

AndersAstad - ‎https://experience.arcgis.com/experience/157c166b18e849a6aaa8606882d19453/page/Page/

Ole_MariusGulbrandsen - https://experience.arcgis.com/experience/3c016ede34fc4936a91bd33c17f3b5c1 and https://experience.arcgis.com/experience/4f40ac3daaad4eb197c39189b53052e5

and they are completely unusable for me. They take around 5 minutes to load and then are almost completely unresponsive to mouse input.

This in both Chrome and Edge.

I have noticed that my CPU usage shoots to 100% whenever I try to load any of these maps, 99% of that usage being my browser. As soon as I close the map window, cpu usage returns to under 5%.

The performance with the classic map viewer and web app builder is absolutely fine.

I have a 40mbps internet connection which is stable and gives me no issues. I have tried on both my work PC (i5-7200 cpu, 8GB RAM) and home PC (i7-7700k, 16GB RAM, 6GB gfx card) and the performance is equally bad on both.

The cause needs to be identified by ESRI and a solution rolled out or advice given as to how to mitigate. If the intention is to eventually retire classic map viewer and web app builder, leaving only the new map viewer and experience builder with this performance issue unresolved, we would have no option but to look elsewhere for our web mapping solution.

Re: Map Viewer is slow, including setting default visualization

RussRoberts — Wed, 05 Apr 2023 14:31:29 GMT

Do you have a support ticket logged to track this issue you are seeing?

I am not seeing it take 5 mins to load.

The first sample takes Finish: 10.82 s

Second: Finish: 9.43 s

Third - not shared to everyone so not able to test.

Re: Map Viewer is slow, including setting default visualization

HighlandCouncil — Thu, 06 Apr 2023 10:44:59 GMT

I've not raised a support call yet but will do so.

For info, I took some timings noted my experience with a couple of the example maps posted above:

https://experience.arcgis.com/experience/3c016ede34fc4936a91bd33c17f3b5c1

CHROME
Took about 5 mins 50 to load. CPU shoots to 100% when loading and stays there once map loaded, making rest of my system unusable. Even typing these observations into Notepad during the load is heavily lagging and the Windows clock I'm using to time it is stuttering and hesitating. Once loaded, map is unresponsive to user input and I would describe as being completely unusable.

EDGE
took about 3 mins 20 load, then experience same as above for CHROME.

https://experience.arcgis.com/experience/157c166b18e849a6aaa8606882d19453/page/Page/

CHROME
Took 6 mins 25 secs until finished loading. CPU at 100% during loading, making rest of my system unusable, but unlike the other map, once finished loading, the CPU settled back to normal and my system became usable again. However, map is again unresponsive to user input (eg. 30 seconds to refresh when panning and CPU shoots to 100%, making the rest of my system unusable until it finished refreshing the map). Again, I would describe the map as being unusable.

EDGE
Took about 3 mins 20 secs until it finished loading, then the experience same as abaove for CHROME.

I asked a colleague to test and they observed that on one device, the load times were ok but on another device (a more powerful desktop PC), it was taking minutes to load.

So performance seems to vary radically from device to device. Given nearly all the maps we (and presumably many other organisations) produce on ArcGIS Online are for public consumption, we need to have confidence they will perform at least adequately for all users and the range of devices they will be using. I currently do not have that confidence with the new map viewer and experience builder.

I will create a couple of examples of my own and log a call. Hopefully the cause of the problem can be found.

Re: Map Viewer is slow, including setting default visualization

MariaGiarrusso — Thu, 06 Apr 2023 12:47:45 GMT

I am experienceing similar Map Viewer performance issues. In our case, it seems to be most problematic when there 8 or more feature services published from Pro in Enterprise 10.9.1. CPU either goes to 100% or is at about 50% for a prolonged amount of time and the MV either gives an incomplete rendering or takes a very long to compete. I have a case open with ESRI and I will share this post with my case. I also see errors in the Dev Console of the browser like net::ERR_CONNECTION_RESET.

I opened your first url on my PC w/ Chrome and Edge and it would not draw at all, yet when I opened in on my phone in the Chrome browser it performed just fine. Also connected to it from my laptop connected to a Verizon Mobile Hot Spot and it was also fine (Chrome and Edge). All of these at roughly the same time.

Re: Map Viewer is slow, including setting default visualization

Miralem_Zeljo — Thu, 27 Jul 2023 20:18:07 GMT

Ever since Esri decided to switch to new Java API we have been having nothing but problems with our maps and applications in AGO. In ArcPRO there is a new feature that was added that allows users to publish layers compatible with all clients - this option is off by default (Not sure if there is option to make it on by default), if you turn it on it makes old applications see symbology however I have seen serious decline in performance speed of maps or applications in AGO. On the other hand if you keep it off - it gives you better advanced symbology and labeling in advanced maps/applications (Experience Builder). Please note that experience builder lacks 60% of the functionality that was available in web app builder and runs at 1/4 of the speed of web app builder when we used old symbology and before new Java was released!

Esri, I am sure your team is aware of this more than us (Standard Users) and I beg you to expedite this problem with your developers so we can go back to using amazing service you had!

I am more than willing to help you troubleshoot this and provide any additional info you may need.

Thank you,