Community

Hosted Map Image Layer in Spatiotemporal Datastore Timing Out in Portal

413
1
07-26-2023 09:27 PM
JessicaRouns
by
New Contributor III
‎07-26-2023 09:27 PM

I have a hosted map image layer in a spatiotemporal datastore with approx 700 mil rows. This service drew fine when there were less rows, but now it's getting chunky it is timing out when drawing in Portal, and is taking > 10 minutes to draw in Pro. The associated feature layer is drawing fine (sub 30 seconds) in both Pro and Portal. 

This data was added to the datastore via GeoEvent server. 

Does anyone have recommendations on spatiotemporal datastore configurations to better support very large map image layers?

Current config;

  • 3 node cluster
  • 16 cores + 64 GB RAM for one node
  • 8 core + 64 GB RAM for other two nodes
  • 5 shards
  • replication factor = 1
  • refresh interval = 60 seconds
  • rolling data = monthly
  • shrink = yes
  • aggregation = hex's to level 12
1 Reply
NicholasEverdell
by
New Contributor II
‎07-26-2023 09:33 PM

Wow, that sounds really backwards to me. Shouldn't a Feature layer load slower than a Map Image layer? 

Unless the compute for the Auto Binning is causing it all to slow down and be unusable by the sound of it.

 

I am sure 700 million dots on a map would look fantastic though!