Local cache directories on the server

In this topic

When many GIS server machines try to write tiles into a shared cache directory at the same time, scalability degrades. For this reason, the server uses a local cache directory to temporarily write tiles on each GIS server.

Local cache directories on the server are only used with caches that use the compact storage type. The server writes one bundle file (which can include up to about 16,000 tiles) to the local cache directory. When complete, the bundle is moved to the shared cache directory. Writing bundles locally and moving them to the shared cache directory is more scalable than having all the machines write the bundles directly into the shared cache directory.

Legacy:

In 10.0 and earlier versions, you could enable or disable the use of local cache directories. In 10.1 and later versions, if ArcGIS Server detects that you have used a shared network folder for your cache directory, the bundle files are always written to the local cache directory first.

Setting the local cache directory location

The default local cache directory is the temp folder for the ArcGIS Server account. You can change this using the ArcGIS Server Administrator Directory.

Create a directory on each GIS server using an identical path. Make sure the ArcGIS Server account has write access to these directories.

Open a web browser to the ArcGIS Server Administrator Directory. The URL is formatted http://gisserver.domain.com:6080/arcgis/admin.

If necessary, log in using a user name and password that has administrative access to ArcGIS Server.

Click system > properties > update.

In the text box, add a localTempFolder property pointing at your folder. For example: {"localTempFolder":"E:\\arcgistemp"}

Click the Update button.

Use Manager or the Catalog window to navigate to the ArcGIS Server folder named System and stop and then start the CachingTools geoprocessing service.

It's recommended that you have at least 0.5 GB of available space in this location for each running instance of the CachingTools geoprocessing service multiplied by the number of GIS servers in your cluster. More space may be required for JPEG or mixed-format caches that use a high compression quality, or detailed PNG caches with high bit depth.