NexusDB

The TCP/IPv4 Transport has quite a few options as well, overlapping with the options for the Named Pipe Transport:

Respond to Broadcast

When this option is active, it instructs the server to send back its identification and version number on broadcast requests received via the regular transport being used.

Compress Limit

Compress Limit sets the minimum number of bytes at which the server initiates data compression for sent messages. If a message size is below that value compression is ignored. The server always responds to compressed requests by compressing the answer, even if the size of the answer is below the compression limit.

Port

Port for TCP/IPv4 is the IP port used for communication. Please note that this has to match with the client side for successful communication.

Adresses

Use the Addresses field to set the TCP addresses the transport will be bound to as a comm delimited list. You can use the asterisk (*) to bind the transport to all available addresses, which is also the the default.

Server Thread Priority

The Server Thread Priority sets, as the name says the priority of the server thread. The server thread of a transport it the one that actually does the work for each request. Be careful with changing thread priorities as there is a fine balance between the different threads of the server needed to achieve optimal performance. For normal processing mode you should generally leave the priorities at their default settings. Valid settings are tpIdle, tpLowest, tpLower, tpNormal, tpHigher, tpHighest and tpTimeCritical.

Concurrent IOCP Threads

Concurrent IOCP Threads is the number of threads processing IOCP (I/O Completion Port) signals. If this number is 0, it means that there is one thread initialised for each processor in the server machine. For general use, this is the optimal setting. For special purposes, it might be useful to change these settings. Please note that this setting is ignored for machines with a Windows version below Win NT. On these machines, IOCP is not available and is emulated and ignores this setting.

Broadcast Thread Priority

Broadcast Thread Priority sets priority for the thread that is responsible for receiving and answering broadcast over for servers

Listen Thread Priority

Listen Thread Priority is the priority for the thread that is responsible for receiving the request and putting it into the Server Thread Queue.

Server Addresses

Again, in the Server Addresses field you see the valid addresses of the server for this transport, which you have to use in the form ServerName@Address for connecting to this server.

As mentioned the various priorities should be left alone unless the user knows exactly what he is doing and its impact on the server performance.