Adjusting Fine Settings (Distribution)

If necessary, you can adapt the distribution precisely to your special needs. Different settings can be set for the distribution to each target.

Frame Size

Files are copied in frames during distribution. Each frame includes a certain specified number of bytes, which are transferred together. After each frame, the copy process is suspended for a predefined period (see below).

Default value: 4096
(Only when DSM is configured the first time, it uses a frame size of 1024)

This setting is available for local depots (distribution to the INSTALL directories) only in sites where package data is compressed (Configuration table setting Keep package data compressed=Yes).

Adjustment factor for minimum activity (%)

Relates to the Minimum Activity setting in the Distribution Timeframe dialog. The interval between frames is increased by the cited factor, e.g., a value of 50%: double interval (1/0.5).

Default: 50%

Polling Intervals

The polling intervals for the three distribution processes are automatically set according to connection type; you can modify them in the configuration table. By default, the polling intervals for the ICDB, repositories and package files are in a relationship of 1: 2: 3.

By setting a polling interval to 0, you „switch off“ the respective distribution process. Doing so, you can e. g. „switch off“ project distribution only.
Setting all polling intervals to 0 has the same effect as „closing“ the distribution timeframe.

Polling Interval for the ICDB [min]

Default: Depending on the connection type

Polling Interval for Repositories [min]

Default: Depending on the connection type

Polling Interval for Package Files [min]

Default: Depending on the connection type

If a copying procedure (for example) for a large _NI5.ZIP file takes so long that a new polling interval is reached, a new distribution process is not started at the polling interval.

Deactivate obsolete Distribution Processes

If several sites use the same server as master depot (so called "logical sites") the data will not be distributed multiple times, so it is recommended that the redundant distribution processes be deactivated.

The easiest way to achieve this, is to set the timeframe in all but one of the relevant sites to "No activity".

If several sites are using the same master depot, the number of simultaneous distribution processes (three per depot) may lead to notable performance losses. For this reason, we recommend not to use several sites with the same master depot.