Original uds mapper

https://maps.udsmapper.org/map

 

Why UDS frequently stroked, sometime extremely slow, almost useless. 

Too much un-used fields uploaded, hurt server performance badly

 

 

https://transparentgov.net/json2tree/esri/server/folder.html?org=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&url=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&select_folder=35&select_layer=0

 

 

 

https://transparentgov.net/json2tree/esri/server/folder.html?org=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&url=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&select_folder=34&select_layer=

 

 

 

 

 

600 fields,  590 is unused, why not remove unused field before upload to arcgis server? So many unused field just exhaust all the computing power of arcgis serve. Result in a very slow, barely responsing, frequently stroked performance

https://transparentgov.net/json2tree/esri/server/folder.html?org=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&url=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&select_folder=12&select_layer=0 

 

 

 

 

https://transparentgov.net/json2tree/esri/server/folder.html?org=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&url=https%3A%2F%2Fags108.healthlandscape.org%2Fserver%2Frest%2Fservices&select_folder=32&select_layer=

 

 

ESRI recommended default is 1000 or 2000, if your arcgis server is slow, then you should reduce this number to 500

Lots of hrsa gis web service set this number from 5000 to 20000 to cover the total feature count, resulting arcgis server stroking frequently. Why they doing that? Because all of their gis app don't have "paging", they have to set this number to cover total feature count. Otherwise their gis app will not function as only export 500 feature to excel as I mentions before.

https://enterprise.arcgis.com/en/portal/10.7/use/server-configuration-details.htm#:~:text=Max%20record%20count%20should%20be,returned%20in%20a%20single%20request.

 

 

by

Please log in or register