AnsweredAssumed Answered

Cached Map Service Tile Rebuild

Question asked by dtenney on Nov 3, 2016

All,

   

   so i have spent some time looking into how to enhance the ManageMapServerCacheTiles process. we noticed that throwing an entire data set at server would sometimes cause our server crash so we came up with a grid concept to break up the work into manageable chunks...

 

Steps... 

   (running Desktop and Server 10.4.1)

1) Bring in New data and compare to Existing Data

2) Create a Delta file  

3) overlay grid on map 

4) force server to rebuild all tiles within Layers 1-13 (not man tiles at those layers so easy to rebuild all) 

5) selectively rebuild tiles in Layers 14-19 (we tell server to reference the delta file within each cell of the grid and rebuild)

   a) repeat this step for all cells of the grid until completed

 

here some initial results of the tile rebuild process...at this point in time we are only about 1/4 of the way done...

 

             Features Per Second
11/2/201611:11.7ProcessedGridID229thathad8184featuresin4669.059seconds1.8
11/2/201648:58.1ProcessedGridID292thathad21011featuresin2266.065seconds9.3
11/2/201615:43.3ProcessedGridID194thathad148362featuresin5204.895seconds28.5
11/2/201640:36.3ProcessedGridID253thathad128679featuresin5091.424seconds25.3
11/2/201601:21.2ProcessedGridID272thathad73952featuresin4844.499seconds15.3
11/2/201605:01.4ProcessedGridID227thathad29831featuresin3818.625seconds7.8
11/2/201618:03.8ProcessedGridID172thathad42387featuresin4381.654seconds9.7
11/2/201616:53.7ProcessedGridID116thathad33044featuresin3529.427seconds9.4
11/3/201618:25.5ProcessedGridID267thathad13923featuresin3691.466seconds3.8
11/3/201657:21.6ProcessedGridID165thathad3317featuresin2334.811seconds1.4
11/3/201646:31.6ProcessedGridID119thathad40912featuresin2949.679seconds13.9
11/3/201644:39.0ProcessedGridID203thathad12641featuresin3487.07seconds3.6
11/3/201633:38.6ProcessedGridID156thathad43882featuresin2938.95seconds14.9
11/3/201640:31.0ProcessedGridID138thathad822featuresin410.9761seconds2.0
11/3/201655:16.9ProcessedGridID214thathad283554featuresin4485.273seconds63.2
11/3/201644:06.2ProcessedGridID284thathad24102featuresin2927.059seconds8.2
11/3/201645:24.2ProcessedGridID183thathad7676featuresin3677.022seconds2.1
11/3/201617:57.4ProcessedGridID190thathad37058featuresin5552.851seconds6.7
11/3/201638:50.7ProcessedGridID55thathad2452featuresin1252.615seconds2.0
11/3/201612:33.4ProcessedGridID188thathad18279featuresin5620.812seconds3.3
11/3/201639:09.2ProcessedGridID276thathad29342featuresin1595.511seconds18.4

 

it seems a bit slow, so a few thoughts:

 

   1) we are obviously constrained by number of cores and how many ArcSOCs we can throw at this process

         ESRI had recommended a "n+1" approach but this all brings the machine down and it ignores any other requests while the process is running, NOT GOOD, so we have decided "n-1" is the safest approach (4-1, so 3 ArcSOCs max)

 

   2) Our mosaic is built from JPEG2000 tiles, does this file type (JPEG2000) cause any overhead which would cause the process to run slower? vs if the mosaic was built from TIFF, SID, JPEG.

 

 

Any thooughts?

 

 

thanks

dave

Outcomes