nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Slow performance when upgrading to API version 4

AdrienFrench

We are upgrading from the JS API version 3.X to 4.24 and we have run into a performance issue when using FeatureLayer objects. Previously we were using ArcGISDynamicMapServiceLayer objects, but these are no longer available in API version 4.

The upgraded version seems to make far more requests to the GIS server and take much longer when panning/zooming around the map. This seems to cause the initial layer load (when we zoom in to a visible scale) to take up 10 seconds, where it was previously less than 1 second.

See the attached screenshots for comparison. In particular, the FeatureLayer seems to make many requests to /query endpoint, whereas the ArcGISDynamicMapServiceLayer does not.

Can anyone offer any explanations as to why this is happening? Is there something I am missing when configuring layers, or am I on the wrong track altogether?

Thanks in advance,

Adrien French

4.x-FeatureLayer-network-requests.PNG

3.x-ArcGISDynamicMapServiceLayer-network-requests.PNG

Find more posts tagged with

Accepted answers

JS_GilbertAZ

I think that MapImageLayer would work, that should do what 3.x ArcGISDynamicMapServiceLayer did. I use multiple MapImageLayers in my app and I have no performance issues.

Ex.

"esri/layers/MapImageLayer",MapImageLayer

dbLayer=new MapImageLayer({
url: svcUrlDB, //rest enpoint url for MapServer
title: "Common"
});

All comments

AdrienFrench

Thank you both for your replies, performance is drastically improved using the MapImageLayer!

RRubalcava

@JS_GilbertAZ is correct.

The 4x equivalent to 3x ArcGISDynamicMapServiceLayer is the MapImageLayer. It has an updated API to make it easier to configure the layers in the service.

In the first screenshot, with the FeatureService, the API is going to request data in cacheable tiles, which can lead extra requests. If you are using multiple FeatureLayers to display the same layers that are in the Map Service, then that would explain the number of requests and possibly slower than expected response if they each contain a good amount of data. MapImageLayer can still perform very fast for Map Services, and if needed you can still create a FeatureLayer from a SubLayer that you an use for queries and more.

JS_GilbertAZ

I think that MapImageLayer would work, that should do what 3.x ArcGISDynamicMapServiceLayer did. I use multiple MapImageLayers in my app and I have no performance issues.

Ex.

"esri/layers/MapImageLayer",MapImageLayer

dbLayer=new MapImageLayer({
url: svcUrlDB, //rest enpoint url for MapServer
title: "Common"
});

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.