Latest Contributions by DaveTenney

I wanted to share more info with everyone and hopefully shed some more light on why this is very perplexing... i have two images attached... 1) AOI - this is running the "managemapservercachetiles" on level 19 whit an area of interest polygon    a. there is very little work to be done with recreating all tiles within the area of interest. 2) ALL - this running the "managemapservercachetiles" on level 18 and level 19     a. there is a lot of work to be doing recreating all tiles in these two levels AOI - memory is running up like crazy and has almost maxed out the machine and is about to fail    a. why would this smaller amount of work cause the memory usage? ALL - the memory usage has stayed consistent at this level throughout the entire process, the cpu usage jumps up and down but i have always seen that behavior. what in the world is going on? ... View more

1) we have roads, addresses, other individual point, and line features. 2) this update process runs on a weekly basis 3) on average we see 20k-50k changes total     a. this is why we do the delta b/c so little changes that we don't want to waste time rebuilding everything 4) when we rebuild tiles we do it in two steps       a. forced scales -  these are level 0-15, very little data total so we just rebuild them all (usually only 10min)       b. selective scales - this is levels 16-19, this is where we implement our area of interest based on the delta results             1) it is within the selective scales that we see the memory usage spike even faster and ultimately failing  5) the sole purpose of this machine/server is to build tiles, nothing else runs on this machine, we did not want anything interrupting this process or bogging down the machine to slow the process. note: i really wanted to separate the vector data from the raster data, i feel that the sheer size of all the data due to them being combined is an issue in itself. the raster data only changes once a year, whereas the vector data changes weekly. the reasoning behind combining them is so we would not have to make two separate requests for the vector and raster data, thus bogging down the bandwidth of the system.      dave ... View more

here is the part in which i get a little confused by everything...    we can run the process manually on level 18 and 19 and recreate all tiles just fine. the minute we utilize an area of interest for those same levels is when we see the memory usage skyrocket.    we had to prove this process in 2 other environments before we could even implement all this in production. this is a behavior we did not see in any of those 2 environments. im not sure where the patches stand for the OS. ... View more

Michael,   i doubt it is pooling as we have taken a conservative approach with the caching services.  we are running the gptools at a max of 3 on a 4 core machine, we did this because we did not want to take the chance to max out the machine. unfortunately, we are now seeing something that runs wild with the available memory. thanks dave ... View more

   Caching services were set to a max of 3, we decided to take the n-1 approach (n = # of cores) in order to prevent the resources from being maxed out on the machine. As for all the services, they run at a max of 2.     yes, i can sit and watch the gptool process run at the same time tracking the machine stats and before too long, the memory just starts jumping up like crazy and ultimately maxing out. ... View more

10 services total: 2 cached map service, 1 dynamic map, 7 locator services we were running 10.2.2, when we upgraded we rebuilt all the services manually using 10.5.1. we were able to rebuild the services manually just fine. now we create an area of interest that is built from a delta check and we get to about level 16 out of 19 and the cachingtools begin consume massive amounts of memory.  we start seeing entries in the cachingtools logs that mention "out of memory", then the process fails. with a similar message: Data access failure, layer = Image, error string = Could not access data for layer or table Image during drawing§TilesWorker: Data access failure, layer = Image, error string = Could not access data for layer or table Image during drawing§TilesWorker: Data access failure, layer = Image, error string = Could not access data for layer or table Image during drawing Failed to cache extent:........ ... View more

Michael,     we are not using suggestions for our results, we found that was providing some pretty dangerous results so we strongly discouraged our client from using them until it was improved upon.    we have 3.5 million addresses for the locator. We did find that there were some issues with the machine so we have decided to step away from this issue until IT has a chance to dive into the machines. So we have moved onto our second issue which i commented on today, it was a thread you were previously involved with. dave ... View more

after opening a ticket with esri support we seem to be making some head way... i am very concerned about the behavior of ArcGIS Server, please see below: i currently have the server set to a max of 2 instances of CachingTools. the two instances of .GPServerSync are crippling our machine! i have never seen this behavior before and the only thing that has changed on our machine is an upgrade from 10.2.2 to 10.5.1 Machine Specs: Windows Server 2012 R2 16 GB Ram Intel Xeon CPU E5-4620 v2  thoughts? dave ... View more

when I attempt to create the locator manually on the machine is "stalls", by that I mean it never finishes creating the locator.  ... View more

the process runs monthly, on 3/5 it last ran and only took 3 minutes to complete. we tried kick off the process this week and it failed, there is no major underlying change to the data.  ... View more

George,     sorry if i wasnt clear, i stated that this locator does NOT exist in a gdb. i put that in there because i had seen a lot of talk about this being an issue for people. Again, the locator is not in a gdb, it is in a folder location all by itself. thanks dave ... View more

My biggest concern would be of bandwidth... 1) current setup where the vector and raster are together, you are only requesting the data once 2) separate services, now you are requesting the data twice(1 request for vector, 1 request for raster) Im not sure if Esri has looking into this or not but that would be the main hesitation on my end. ... View more

the imagery is only updated once a year, it is the vector data that is updated on a weekly basis. yes, we create a RMD from the jpeg2000 raw tiles. ... View more