Batch Server Advanced Settings - trillium_geolocation - 15.19

The Batch server limits the maximum number of clients that can be connected simultaneously. This defaults to 50. To modify this setting, change the <Value> entry in the Max Sessions option in the <BatchServerOptions> section. (Note that the number of clients is also restricted by memory.)

<BatchServerOptions>
   …
   <Option>
      <Name>Max Sessions</Name>
      <Value>50</Value>
   </Option>
   …
</BatchServerOptions>

The Batch server imposes a timeout on the port used for informational requests (the “stats port”). This defaults to 10000 milliseconds. To modify this setting, change the <Value> entry in the “Stats Socket Timeout” option in the <BatchServerOptions> section. The timeout is specified in milliseconds.

<BatchServerOptions>
   …
   <Option>
      <Name>Stats Socket Timeout</Name>
      <Value>10000</Value>
   </Option>
   …
</BatchServerOptions>

The Batch server limits the number of threads that are used when processing each Batch job. This defaults to 1. To modify this setting, change the <Value> entry in the “Num Threads” option in the <BatchServerOptions> section:

<BatchServerOptions>
   …
   <Option>
      <Name>Num Threads</Name>
      <Value>1</Value>
   </Option>
   …
</BatchServerOptions>

The “Split Threads Between Servers” setting works in conjunction with the “Num Threads” setting. It specifies whether the threads should be split between all of the available Trillium Geolocation servers. If this is set to false, all threads will use the first available Trillium Geolocation server.

<BatchServerOptions>
   …
   <Option>
      <Name>Split Threads Between Servers</Name>
      <Value>true</Value>
   </Option>
   …
</BatchServerOptions>