Performances for tile creation and retrieval of cache tiles for map services using map caching on demand are very slow.
Last Published: April 7, 2016ArcGIS for Server
Bug ID Number
April 13, 2015
July 28, 2020
ArcGIS for Server
Operating System Version
2008 R2 64 Bit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
The developers looked into this and found no further improvements can be made to the performance of cache on demand.
We recommend "cache on demand" only for the areas that are expected to have least traffic at large scale levels.
Never use "on-demand” caching to build your entire cache. You should always precreate some tiles in the areas of the map you expect to have the most user traffic, thereby minimizing the chance that a user will consume server resources by requesting a tile on demand.
The process of generating cache on demand is expected to be slow, as mentioned in our documentation:
“when you use on-demand caching, the server does have to draw tiles dynamically when a user navigates to an uncached area. This dynamic drawing actually takes longer than a regular request because the server creates a group of tiles at once. This group of tiles is 2048 x 2048 pixels in dimension if the map service uses antialiasing and 4096 x 4096 if it does not”
Hence it is recommended to use “cache on demand” wisely.
We recommend that users should optimize their map documents to meet the fast response times expected by web users. Check the “Testing & optimizing map” section in the following help topic. If the data is taking a long time to draw and cannot be optimized It is recommended that they should pre-cache the mapservice.