Before you start to tune the performance of an Application Object Server (AOS) instance, trace the usage of the AOS instance to ensure that you understand the performance under the current settings. For information about tracing and monitoring AOS performance, see Optimizing performance.

Before you implement tuning changes in a production environment, test them all. In a test or development environment, make one change and then test your system's performance before making another change.

You can adjust many options to tune your system, including:

  • Adjust the maximum allowed sessions and memory use for an AOS.

  • Set a group of AOS instances to load balance.

Adjust maximum sessions and memory use

If after you run your Microsoft Dynamics AX implementation you find that your system performs best when at or under a certain load, you can adjust the values of the following configuration commands in the configuration file of the AOS. After you set any value, you must restart the AOS for the change to be applied.

  • MaxConcurrentUISessions- Sets the maximum number of concurrent Microsoft Dynamics AX client sessions. The default value is 65535.

  • MaxConcurrentGuestSessions- Sets the maximum number of concurrent Guest (anonymous user) sessions. The default value is 65535.

  • MaxConcurrentWebSessions- Sets the maximum number of concurrent Enterprise Portal sessions, including Guest sessions. The default value is 65535.

  • MaxConcurrentBCSessions- Sets the maximum number of concurrent Business Connector sessions, including all Web sessions (all Web sessions come through Business Connector). The default value is 65535.

  • MaxMemLoad- Sets the maximum amount of memory usage (the maximum percentage of physical memory that is in use on the computer). The default value is 100.

  • MaxConcurrentSessions- Sets the maximum number of client sessions an AOS instance will accept. The default value is 65535.

    Note Note

    MaxConcurrentSessions is the only value that affects load balancing. If you load balance, do not use any MaxConcurrent< option>Sessions value or the MaxMemLoad option to tune performance.

For details about using these commands, see Using the command line to manage the AOS.

Set up load balancing

You can load balance across multiple computers that are running Microsoft Dynamics AX Application Object Server (AOS) instances.

The options for a load balancing topology include:

  • Add AOS instances to a cluster and run the cluster without a load balancer.

    If you set up a cluster without a load balancer, you can use client configurations to set clients to connect to one or more AOS instances that have load balancing enabled. If an administrator needs to remove a computer from the cluster, and one or more client configuration is pointing to it, the client configuration must be updated. No additional hardware is required for this topology.

  • Add AOS instances to a cluster and configure one or more AOS instances to be a load balancer.

    If you set up a cluster with a load balancer, you must use client configurations to set clients to connect to the AOS that has been set as the load balancer. You can then add and remove instances from the cluster without needing to update client configurations. Additional hardware may be required to set up a computer as a load balancer.

For details about setting up and managing load balancing, see Cluster maintenance.