Tips for optimal performance

Use these recommendations to achieve optimal performance of your Deployment Automation installation.

To ensure optimal performance:

  • Install the server as the root user or system user account.

    The server must be installed as the root user on UNIX/Linux and as a local system user on Windows. Running in this manner avoids all permission errors. Deployment Automation needs this level of permissions because it writes into protected location such as /opt and /var/opt.

  • Install each agent as a dedicated system account.

    Ideally, the account should only be used by Deployment Automation. Because Deployment Automation agents are command execution engines, we recommend that you limit what they can do on host machines, by creating dedicated users and then granting them appropriate privileges.

    If you install an agent as the root user (or local system user on Windows), ensure that agent processes cannot adversely affect the host file system.

  • Install a single agent per host machine.

    If multiple agents are running on the same machine, they can negatively impact each other's performance. If you install multiple agents on the same machine, ensure the machine has adequate capacity to meet the system requirements for all the agents. Otherwise, you may have performance issues when multiple agents are busy simultaneously.

  • Install component integrators.

    If you plan to regularly import large numbers of files from an external source, use component integrators to take the load off the server. The server delegates the tasks of downloading and storing artifacts to component integrators, without engaging its own resources.

    Component integrators support some but not all external source configuration tools. Check whether the sources with which you work are supported.

    For better load distribution, install multiple component integrators on multiple machines in various locations.

  • Configure system components to use more secure protocols.

    By default, Deployment Automation allows the use of TLSv1.2, TLSv1.1, and TLSv1 protocols. You can make your system communication more secure by allowing TLSv1.3 and TLSv1.2 only.

    To change the default configuration after the installation or upgrade, edit the files for your server, agents, agent relays, and component integrators, and replace the default protocol list with the following line:

    TLSv1.3, TLSv1.2

    All your system components must be set to use the same protocols.

Back to top

See also: