Map layer performance threshold

1629
3
03-24-2017 02:30 PM
AndyWright
Occasional Contributor

We've got a Xamarin Forms application that, for the most part, runs and performs pretty well.  We started to see some performance degradation in the map with a new customer's data so we decided to do some hard core performance testing on it to try to find the breaking point.  The last test I performed loaded around 2000 feature layers from a SQLite geodatabase into the map and the map performance was horrible and the app was consistently crashing with unhandled exceptions.  Interestingly enough, all but a handful of those layers were turned off so I figured things would be ok since 99% of the data was not being rendered.  It seems that the presence of all that data, whether it's turned on or not, has a negative impact on the map doing its job efficiently.  And performance started degrading long before I got to 2000 layers.

I guess this is not unexpected behavior, but I'm interested to hear from the Esri folks on this stuff.  Have you guys done any performance testing on the map control and can you let us know what types of limits you've found?  Obviously volume of data within each layer comes into play here in addition to the way the layers were setup in the source MXDs and APRXs, but all things being equal what should we expect ?

0 Kudos
3 Replies
dotMorten_esri
Esri Frequent Contributor

2000??? I think you just hit the record for most layers a user has attempted to add to a single map :)

Our recommendation is to keep these under 10-20 layers, we'll handle more, but especially on mobile devices, to keep plenty of resources reserved for the rest of the app - it's also an app easier to manage by the user. Each layer adds significant texture memory usage to the GPU as well as CPU overhead. Your crashes are most likely due to GPU exhaustion.

I've rendered feature layers with 100000s of features in it. Map stays pretty responsive, although the layer update frequency could be affected a little. However adding that many individual layers is not what we optimize for.

0 Kudos
AndyWright
Occasional Contributor

Thanks for the reply Morten.  This gives us something to go on and something to frame the conversation with our customers.  

0 Kudos
MichaelBranscomb
Esri Frequent Contributor

Hi,

Work was done to improve performance in this area for the v100.2 release (although the previous guidelines regarding the number of layers still generally apply).

Please download the latest Visual Studio extension from ArcGIS for Developers or update your NuGet packages via the NuGet package manager.

Cheers

Mike

0 Kudos