TUNING

Primary and secondary goals for resource balancing
To balance resources, first determine your primary and secondary goals, and specify how much weight to give each of these goals. The default goals are Notes® Transactions and Disk Space, which are the defaults for Primary and Secondary goals respectively. Because transactions factors in almost all user and server activity, and disk space is typically a constrained resource, these are a good measurement on which to balance.

The second factor in resource balancing is tolerance. When you specify tolerance, you indicate the level of accuracy you want for the resource. A low value typically generates more moves (it is less tolerant), but produces a better distribution of the resources that are closer to the targeted accuracy. A high tolerance value creates fewer moves, but does not distribute the activity as evenly. You set tolerance values for both the Primary and Secondary Goals, however the primary tolerance is much more important than the secondary tolerance in determining the number of moves.

Finally, you specify whether to use trended data or data collected from one observation period. You also choose when to gather the data.

The resulting resource chart may show heavy activity on some servers and light activity on others. You can choose to balance the activity across the servers so that no single server shows a high incidence of activity. You can balance resources based on a primary and a secondary goal. Unless you have specific requirements in mind, the recommended primary and secondary goals are Notes Transactions and Disk Space, respectively.

Because the primary goal is given more weight than the secondary goal, set the resolution of the most troublesome resource area as the primary goal. For example, if you suspect that some servers have available disk space, while others have almost none, choose the statistic Disk Space as the primary goal.

Table 1. Statistics by name
Statistic NameDescription
AvgSpaceUsedPercentage of the disk space actually in use, as recorded by the database activity data.
DiskSpaceThe number of bytes of disk space occupied by the database, as recorded by the database activity data.
FullTextIndexSizeSize of the full-text index for this database.
HTTP BytesFromServerThe number of bytes sent from the database, as recorded by the user session data.
HTTP BytesToServerThe number of bytes sent to the database, as recorded by the user session data.
HTTP RequestMsecsRequest time, in milliseconds.
HTTP RequestsThe number of HTTP requests.
Notes BytesFromServerThe number of bytes sent from the server, as recorded by the user session data.
Notes BytesToServerThe number of bytes sent to the server, as recorded by the user session data.
Notes ConnectsThe number of database connections, as recorded by the user session data.
Notes DocumentsReadThe database read count, as recorded by the database activity data.
Notes DocumentsWrittenThe database write count, as recorded by the database activity data.
Notes TransactionsThe number of transactions, as recorded by the user session data.
Replica BytesReadThe number of bytes read, as recorded by the Replicator task.
Replica BytesWrittenThe number of bytes written, as recorded by the Replicator task.
UsersThe count of unique users, as recorded by the user session data.

Related concepts
Understanding how Activity Trends collects data

Related tasks
Setting primary and secondary resource-balancing goals
Setting up resource balancing in Activity Trends
Specifying database and server locations for resource balancing