Tuning Server Settings
AM has a number of settings that can be tuned to increase performance.
Logging Settings
The following general points apply:
Set debug logging level to
error.Set container-level logging to a low level, such as
errororsevere.
Notification Settings
AM has two thread pools used to send notifications to clients. The Service Management Service (SMS) thread pool can be tuned in the AM console under Configure > Server Defaults > SDK > Data Store:
| Property | Default Value | Suggestions |
|---|---|---|
| Notification Pool Size | 1 | Specifies the size of the thread pool used to send notifications. A value of ( |
The session service has its own thread pool to send notifications to listeners about changes to CTS-based sessions. This is configured under Configure > Server Defaults > Session > Notification:
| Property | Default Value | Suggestions |
|---|---|---|
| Notification Pool Size | 10 | This is the size of the thread pool used to send notifications. In production this should be around 25-30. ( |
| Notification Thread Pool Threshold | 5000 | This is the maximum number of notifications in the queue waiting to be sent. The default value should be fine in the majority of installations. ( |
Session Settings
The Session Service has additional properties to tune, which are configured under Configure > Server Defaults > Session > Session Limits. The following suggestion applies to deployments using CTS-based sessions:
| Property | Default Value | Suggestion |
|---|---|---|
| Maximum Session Cache Size | 5000 | Maximum number of AM sessions to cache on the server. In production, this value can safely be set into the 100,000s. The maximum session cache size is really controlled by the maximum size of the JVM heap which must be tuned appropriately to match the desired session cache size. ( |