Performance Tuning Guide - EMC Community Network
Performance Tuning Guide - EMC Community Network
Performance Tuning Guide - EMC Community Network
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Maximizing Process Throughput<br />
Increasing polling intervals for multiple Content Servers<br />
The workflow agent polls the database by issuing two queries to the database each time the polling<br />
interval expires. If your deployment comprises eight Content Servers, eight workflow agents (one for<br />
each Content Server) poll the database. A polling interval of 5 seconds for each of these 8 Content<br />
Servers results in 8 x (60/5) x 2= 192 queries a minute to the database or 11,520 queries per hour. In<br />
contrast, a 5-minute polling interval results in only 96 queries an hour.<br />
To compensate for the increased load on the database that polling from multiple Content Servers<br />
creates, increase the polling intervals for each Content Server incrementally by the amount of the<br />
polling interval for one Content Server. For example, if the polling interval for one Content Server is<br />
15 seconds, set the polling interval for two Content Servers at 30 seconds, three Content Servers at<br />
45 seconds, and so on.<br />
Configure the workflow agent for all (equally sized) Content Servers in a multi-server deployment the<br />
same way, except if one Content Server also services TaskSpace. If one Content Server also services<br />
TaskSpace, configure it differently to ensure sufficient levels of TaskSpace performance.<br />
Configuring the polling interval<br />
The following example uses IAPI to configure the polling interval for 30 seconds:<br />
API> retrieve,c,dm_server_config<br />
API> set,c,l,wf_sleep_interval<br />
SET> 30<br />
API> save,c,l<br />
Note: The repository must be restarted for these configuration changes to take effect.<br />
Configuring for on-demand processing<br />
Content Server can be configured to process automatic workflow activities as soon as they are created.<br />
This configuration provides the lowest latency and is useful for test systems or when there are few<br />
users (low load) and few automatic activities (low throughput). Enable on-demand processing by<br />
setting the following environment variable for your operating system:<br />
DM_NOTIFY_WF_AGENT_AUTO_TASK=T<br />
With on-demand processing, Content Server immediately notifies the workflow agent upon<br />
creation of an automatic activity and does not wait for the polling interval. When using on-demand<br />
processing, set the polling interval high to enable Content Server and workflow agent to complete<br />
their transactions long before expiration of the polling interval. Setting the polling interval to 300<br />
seconds generally provides the best throughput.<br />
Note: Use polling for Content Servers with workflows launched more frequently than every<br />
3 seconds.<br />
<strong>EMC</strong> Documentum xCP 1.0 <strong>Performance</strong> <strong>Tuning</strong> <strong>Guide</strong> 31
Change language