Transformer - Investigate what can be optimized and configured in the Koop instance to handle large data set
As a GIS Analyst, I want to review and discover possible optimization and configuration changes that can be made for the MVP release.
Acceptance Criteria:
- Strategy to optimize the process
- Better set of expectations
- Known issues item added to document this issue
Possible options:
- Investigate Vector Tiles for long term solution
Comments from Levi
@Philip Dougherty – In testing the 186,497 records in Koop, we found that we could display the points in a map after adjusting the maxRecordCount of our Koop Feature Service to 190,000. When it was previously set to 5,000, Postman and ArcGIS Online could only see 5,000 points. ArcGIS Online did not like displaying 180,000 points at once with our existing configuration.
I assume there are optimizations / configurations to be made on the Koop side to enable caching/batching for better handling of large datasets. Do you have any insight into the Feature Layer configurations within Koop that would support performance on this scale?