Experience Builder speed with large number of layers

[ThomasIllingworth]

Hello Everyone

I was wondering how you all find experience builder copes with a web map that has a large number of layers to deal with?

This doesn’t mean they are turned on by default just with the initial loading I’ve found that it seems to struggle with loading a large web map with 180 layers in most off by default. With only two simple boundary layers on to start with everything is limited scaled etc as we do for all maps.

I find the layer widget seems to struggle quite a bit with the initial loading once loaded it seems to behave but the load time can be sometimes as long as a minute.

I was wondering with how people have made experiences with large numbers of layers not necessarily all on by default more performant?

All the layers are coming from our own ArcGIS Server stand alone site split across 3 services which when testing performance work well

[JudithWammack]

This is our Public Web Map for the county. It contains about 100 layers, with only a few turned on by default, and additional layers activating as you zoom in. We experience a lot of rendering problems, both for users on virtual machines and for regular users outside of virtual machines.

At this time, all of our users are accessing the map through Google Chrome.

Regular users need to make sure they are updated to the newest version of Chrome. They also have to go into Chrome settings under System and enable “Use graphics acceleration when available.”

Virtual machine users need to be updated as well. In addition to enabling “Use graphics acceleration when available” in the Chrome system settings, they also need to go to chrome://flags and enable “Override software rendering list.”

I don’t currently have any regular users doing the override rendering, but that might be an option for you. These are computers that do not have graphic cards.

[DougBrowning]

Same issue here but the issue seems to be more with new map viewer.  It "touches" every single layer at load where old map viewer did not.  Test old and new map viewer to see if that is it first.