Skip To Content

Locator performance properties

This topic describes the properties listed in the Performance section of the Locator Properties dialog box.

Learn more about modifying a locator's settings


For optimal performance with larger locators it is recommended that they are stored on a Solid State Drive. The locators can also be warmed-up prior to use to load locator indexes into the cache. Warm-up can be done for a locator by placing a file named warmup.txt in the same directory where the locator is published. The warmup.txt file should contain a single address per line and should limit the number of addresses in the file to 50 or less because it could cause the service to timeout when starting up.

Data cache size

This is the amount of RAM in megabytes the locator can allocate for caching the reference data of the locator. Geocoding will be faster as more data is cached in the memory when the data cache size is increased.

Follow the steps below to change the amount of memory allocated to caching reference data:

  1. On the Locator Properties dialog box, click the Performance tab on the left.
  2. Click the text box under the Data cache size option, and enter a new number in megabytes.
  3. Click OK to save the setting.

Presort input table by (fields)

This determines the sorting order, by field name, of the input table. If the locator is large, parts of the reference data in the locator are cached in the computer's memory for fast access. Therefore, it's more efficient to geocode a table that is sorted by geography, such as state name, ZIP Code, and city name, because the inputs can be compared faster with the data that is currently in the cache. On the other hand, if the records in the input table are not sorted and the inputs are scattered over a large area, it may take a longer time to geocode. The Presort input table by (fields) option allows the geocoding process to sort the records on the fly based on the specified fields.


If records in the table are already sorted, this option may not provide a performance improvement.

  1. To change the presort field setting, click the Select presort fields button Select presort fields next to the Presort input table by (fields) box.

    A fields context menu opens.

  2. Choose the fields you want to use for sorting in the Input fields list by checking the boxes associated with each field.

    The field names in the list are in the order the records would be sorted. To change the sort order of the fields, click a field name in the list and use the Move Up Move Up or Move Down Move Down buttons to move the name up or down in the list.

Presort cache size (number of records)

This is the number of records in the presort cache. This option only applies if input table fields are specified in the Presort input table by (fields) option. A subset of data in the input table, defined by the presort cache size, is cached in the computer memory. The records are sorted and geocoded. The process repeats on the subsequent subsets of the data until the table is completely processed.

You can change the presort cache size on the Locator Properties dialog box by following the steps below.

  1. Click the text box under the Presort cache size (number of records) option, and enter the number of records that you want to cache for presorting.
  2. Click OK to save the setting.

Number of threads

This setting refers to the number of threads that are used for geocoding. To improve geocoding performance, it is recommended to use multiple threads. The capacity is determined by the number of processors available. You can set the property to Auto if you want it to be determined automatically.

Multithreading on a composite locator, which also needs to be in the same file folder as the participating locators, is determined by the setting of each participating locator. Each participating locator will create its own predefined number of threads.

Multithreading options are also honored for locators published as geocoding services running on ArcGIS for Server.

Maximum number of candidates

This is the maximum number of candidates to be returned in interactive match or rematch. Once the maximum number of candidates is returned, the search stops.

Maximum number of perfect candidates

This is the number of perfect match candidates (in other words, a score of 100) that are to be returned in interactive match or rematch. Once the maximum number of perfect candidates is returned, the search stops.

Search time-out

This value, in seconds, sets the time-out for the candidate search. For a locator that covers a very large area and contains many candidates of similar content, a common address without specific zone information, such as 100 Main Street, may take a longer time to search. Setting a search time-out limits the amount of time you spend waiting for a result, but since the time-out causes the search to stop prematurely, potential candidates may be overlooked, and the best location may not be found. The recommended practice is to provide more complete input information so the search can be more efficient.

Maximum number of suggest candidates

This is the maximum number of suggest candidates that will ever be returned even if the user requests more when using the maxSuggestions parameter of the suggest operation in the geocoding REST API. This property is only supported for locators that support suggestions that are published as geocode services with that capability enabled.