Increasing the number of concurrent Sun Management Center console user sessions incurs a modest increase in load on the server layer. The sizing estimates assume 5 active users for a small configuration, 10 users for a medium configuration, and 15 users for a large and extra-large configuration. The sizing estimates assume the users are performing activities such a browsing managed property data and events and editing property attributes.
Some user-initiated actions might temporarily affect the performance of the server layer for the duration of the operation.
Large group operations that are targeted at 100 or more agents can consume significant server resources. These operations can further affect server performance if the changes generate alarms on the managed agents. These alarms produce additional management activity in the form of event processing.
Network discovery operations involving the addition of many new entities for the server to manage can incur noticeable load on the server layer host during the discovery process.
Topology data import operations involving the addition of many new entities to manage can result in slower response from the server layer while the entities are being added.
The effect of these user-initiated actions can be minimized by not executing these operations concurrently, by breaking up large operations, and, when possible, by performing or scheduling the operations during off-peak hours.