Use Minimum Clients per Server (-Mi) to specify the number of remote users on a server before the broker starts another server (up to the maximum number of servers).

n

The number of remote users on a server before the broker starts another server. See also the Maximum Servers (-Mn) startup parameter.

This parameter pertains only to multi-user versions of OpenEdge. In addition, -Mi and -Mn apply only to databases accessed from remote network nodes.

As remote users enter the database, the broker process starts just one server process for each n remote users, until the maximum number of servers (specified by the Maximum Servers (-Mn) parameter) is started. If you specify a value of 1, the broker starts a new server for each of the first -Mn remote users. Subsequent remote users are distributed evenly among the servers until the maximum number of users (-n) or maximum clients per server (-Ma) limits are reached.

Typically, you can leave -Mi and -Mn at their default values. If you significantly increase -Mn, you should also increase -Mi. For example, if you set -Mn to 10 to accommodate up to 40 or more remote users, increase -Mi to 3 or 4 to prevent a situation where 10 servers were started for just 10 remote users.

The Minimum Clients per Server (-Mi) parameter may be modified while your database is online using PROMON or through the _DbParams VST. This change will only take effect on the primary broker and its servers. Online changes to existing secondary brokers will require a restart.