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; } } }

High memory usage with 50-600k point geometries

Espen_RøvikLarsen

Hi,

The memory usage easily exceeds 2GB and can reach the magic number that crashes a 32bit application on Windows.

I see that I am not the only one experiencing this. I am using the recommended optimizations and I have tried different modes (static, dynamic). The graphics are added to a GraphicsOverlay and I am using a renderer to define symbolization (v10.2.7 / v100.0 / v100.1).

Will this issue be improved upon in a forthcoming release?

Find more posts tagged with

Accepted answers

All comments

Espen_RøvikLarsen

I am changing jobs and I will probably not work with ESRI software for a long time. In the process I do not have the time to make you an app.

That being said there is no complexity to this. It happens for point geometries in large volume.

SomeGISGuy

Is it possible for you to build a small stand-alone reproducer that reproduces this? (ie something that generates random graphics/features with similar a amount of geometries with similar complexity and attributes)

Espen_RøvikLarsen

That would be an alternative yes, but as the data is coming over a generic REST call (non-ArcGIS) the orchestration would be a bit heavy.

From a programmers perspective I am really curious about how megabytes of data turns into gigabytes inmemory. Is there some kind of bitmap caching behind the scenes?

SomeGISGuy

You should see the best performance with large datasets by using a runtime geodatabase

Espen_RøvikLarsen

I see, the load time would surely increase. But the main blocker is the memory usage. I am forcing GC collect, and I can see that most of the memory usage is unmanaged.

SomeGISGuy

Did you use the Add method that adds an entire array of them? If you do one-by-one yes it'll be slower. You can't really rely on the memory consumption - it could just be the GC decides it's not low on memory and busy doing other stuff, so will hold off on collecting memory.

Espen_RøvikLarsen

Thanks for the tip. I tried it now - still 600MB for 160K items. The load time went from a few seconds to a minute. Probably due to the async API for adding a feature to the feature table - lots and lots of garbage collections.

I know the actual data is about 15MB in memory, so I am curious about what the runtime is doing.

SomeGISGuy

Have you tried using FeatureCollectionLayer with a FeatureCollectionTable instead?

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.