Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Configuration tuning

  • Last UpdatedApr 24, 2025
  • 1 minute read

The BLTHost process allows certain Windows Communication Foundation (WCF) and threading parameters to be overridden. Caution should be taken when modifying these settings and thorough testing conducted.

Note: Changing these settings will affect all BLTHosts running in a particular silo (for example, Common or RealTime).

For more information on how to override the following settings for the CoreSDK product name, contact AVEVA Customer Support.

Setting

Description

BLTMAXCONNECTIONS

Maximum number of connections to be pooled for subsequent reuse on the client and the maximum number of connections allowed to be pending dispatch on the server. The default value is 50.
https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.nettcpbinding.maxconnections

BLTHOST_MIN_WORKERPOOL_SIZE

The minimum number of worker threads that the thread pool creates on demand. The default is 0, which allows the call to SetMinThreads to be the number of processors on a system.
https://docs.microsoft.com/en-us/dotnet/api/system.threading.threadpool.setminthreads

BLTHOST_MIN_IOPOOL_SIZE

The minimum number of asynchronous input-output (I/O) threads that the thread pool creates on demand. The default is 0, which allows the call to SetMinThreads to be the number of processors on a system.
https://docs.microsoft.com/en-us/dotnet/api/system.threading.threadpool.setminthreads

BLTHOST_MAXCONCURRENTCALLS

Specifies the maximum number of messages actively processing across a BLTHost. The default is 16 times the processor count.
https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.description.servicethrottlingbehavior.maxconcurrentcalls

BLTHOST_MAXCONCURRENTSESSIONS

Specifies the maximum number of sessions a BLTHost object can accept at one time. It also sets the maximum number of queued connection requests that can be pending. The default is 100 times the processor count.

  • https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.description.servicethrottlingbehavior.maxconcurrentsessions

  • https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.nettcpbinding.listenbacklog

BLTHOST_MAXCONCURRENTINSTANCES

Specifies the maximum number of InstanceContext objects in the service that can execute at one time. The default is 116 (BLTHOST_MAXCONCURRENTCALLS + BLTHOST_MAXCONCURRENTSESSIONS) times the processor count.
https://docs.microsoft.com/en-us/dotnet/api/system.servicemodel.description.servicethrottlingbehavior.maxconcurrentinstances

Related Links