The POA uses its client/server processing threads for priming users' Caching mailboxes and for moving users' mailboxes from one post office to another. By default, the POA can use as much as 20% of its client/server threads for these activities. If many users are starting to use Caching mode or are being moved, you can increase the amount of POA resources devoted to priming and moving.
The Maximum C/S Thread Usage for Cache Priming and Live Moves page lets you control the percentage of POA threads used for these activities for the current POA session. Increasing thread usage so that priming and moving proceed more efficiently might impact GroupWise® client responsiveness for other users.
Standard thread usage is established in ConsoleOne® (POA object > GroupWise tab > Agent Settings page > Max Thread Usage for Priming and Moves field).
Displays the maximum number of users that can be creating their Caching mailboxes at once. The maximum number depends on the total number of client/server processing threads the POA has been configured to start and the percentage of those threads that can be used for priming Caching mailboxes and moving users.
Specify the maximum percentage of client/server threads that you want the POA to use for priming Caching mailboxes and moving users, then click Submit to put the setting into effect.
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.