Hello everyone,
I have a map service that is a cached aerial image. It’s published to my federated portal server (11.1). It performs relatively well but I've always wondered if I could make it a bit snappier in terms of draw speed. I don't need any kind of analysis/querying for it, so I’ve been reading into hosted raster tiles as a way to potentially speed it up. Would a hosted raster tile layer perform that much better than a cached map service?
I’ve saved a service definition, published it using my server manager, and then gone into the tile building portion of the layer settings as recommended by this ESRI documentation, and the expected cache size is 44+ gb. I've also run an estimator when publishing directly from Pro (choosing Tile from the Copy Data options) and that estimate was north of 26 gb. I don’t know exactly where that will write to (I expect the server machine’s D drive but I can’t say I’m 100% sure). That file size isn't necessarily prohibitive, but I tried to save a service definition file earlier in my testing and while the estimated size was around 45 gb, the actual file size exceeded 90 gb, which pushed up against the remaining storage on the machine and I had to kill the whole process before it crashed the server.
Any thoughts before I press play on this one? I'm curious what others have done to maximize performance of raster layers in their web environments.
Happy mapping,
- Zach
