Pooling
Use the Pooling page to specify the minimum and maximum number of instances of the geoprocessing service that can run on the server at any one time. Because of the way the server shares these instances among clients, it may be that the number of clients you can support is greater than your number of running instances. For more information about pooling, see Tune and configure services. For general tips for setting pooling properties, see Anticipate and accommodate users.
Timeouts
| Parameter | Explanation |
|---|---|
The maximum time a client can use a service | The maximum time, in seconds, that a service can be used. You may need to increase the default of 600 seconds (10 minutes) for long-running geoprocessing tasks. Alternatively, you may need to reduce this time to ensure a client will not abuse your services. |
The maximum time a client will wait to get a service | The maximum time, in seconds, that a client will wait to connect with an instance before timing out. When all instances are busy processing requests, subsequent requests are queued. If this time-out elapses before an instance becomes available, the task will fail. The default is 60 seconds (1 minute). |
The maximum time an idle instance can be kept running | The maximum time, in seconds, that an instance will continue to be active before pool shrinking occurs. Any instances above the minimum number of instances that have not been used will be shut down once the idle maximum time value has elapsed. |
Processes
Use the Processes page to specify how the geoprocessing service will run on the server. The Tune and configure services topic gives a high-level overview of the considerations you should take into account when setting isolation and determining recycling intervals.
Note:
Geoprocessing services are only run in high isolation.