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.
Measuring <strong>Performance</strong><br />
(the back-end infrastructure from the application server down to disk drives). Single user testing<br />
involves the following steps:<br />
1. Determine the transactions to measure.<br />
2. Prepare a quiet application server.<br />
3. Warm up the system.<br />
4. Turn on DFC tracing.<br />
5. Execute the business transaction.<br />
6. Turn off DFC tracing.<br />
7. Process and analyze your trace files.<br />
Determine transactions to measure — Determining the business transaction and breaking it into<br />
distinct and separate steps is critical. There is no rule here other than your choice of what you wish to<br />
measure and potentially improve. An example of a business transaction is "Hockey Team Canada<br />
just won the gold medal, I must find a picture of the winning goal". This business transaction can<br />
be broken into the following steps:<br />
1. Search for keywords "hockey" and "canada" and display list of results.<br />
2. Click the "get me next page" icon.<br />
3. Click image to view properties.<br />
4. Export the image to local drive for publication composition tools.<br />
Prepare a quiet application server — Use a quiet application server to ensure your trace files do not<br />
become contaminated by other users of the system. This requirement is especially important when<br />
tracing is done on a production system or you are unable to declare the application server as off-limits.<br />
Warm up the system — Warming up the system is like warming up the Oracle library cache.<br />
Warming up the system makes sure one-time activities (caching of the BOF jar files, for example)<br />
do not affect actual measurements. It is also critical that you use the correct data to avoid (or not)<br />
caching at either the database layer (the Oracle buffer cache, for example) or the storage array layer<br />
(the vmax cache, for example). For example, you can search for one keyword during warm-up and<br />
another when collecting traces. This way, your results are unlikely to be in the database or storage<br />
layer cache, unless you want to test response times when data is cached at these layers.<br />
Turn on DFC trace — Turn on the DFC trace file collection by setting the following in<br />
dfc.properties file:<br />
# tracing<br />
dfc.tracing.enable=true<br />
dfc.tracing.file_prefix=dam_prefix<br />
dfc.tracing.include_rpcs=true<br />
dfc.tracing.include_session_id=true<br />
dfc.tracing.max_stack_depth=0<br />
dfc.tracing.mode=compact<br />
dfc.tracing.timing_style=seconds<br />
dfc.tracing.verbose=true<br />
dfc.tracing.verbosity=verbose<br />
72 <strong>EMC</strong> Documentum xCP 1.0 <strong>Performance</strong> <strong>Tuning</strong> <strong>Guide</strong>
Change language