Performance Tuning Guide - EMC Community Network

More documents

Recommendations

Info

Measuring Performance (the back-end infrastructure from the application server down to disk drives). Single user testing involves the following steps: 1. Determine the transactions to measure. 2. Prepare a quiet application server. 3. Warm up the system. 4. Turn on DFC tracing. 5. Execute the business transaction. 6. Turn off DFC tracing. 7. Process and analyze your trace files. Determine transactions to measure — Determining the business transaction and breaking it into distinct and separate steps is critical. There is no rule here other than your choice of what you wish to measure and potentially improve. An example of a business transaction is "Hockey Team Canada just won the gold medal, I must find a picture of the winning goal". This business transaction can be broken into the following steps: 1. Search for keywords "hockey" and "canada" and display list of results. 2. Click the "get me next page" icon. 3. Click image to view properties. 4. Export the image to local drive for publication composition tools. Prepare a quiet application server — Use a quiet application server to ensure your trace files do not become contaminated by other users of the system. This requirement is especially important when tracing is done on a production system or you are unable to declare the application server as off-limits. Warm up the system — Warming up the system is like warming up the Oracle library cache. Warming up the system makes sure one-time activities (caching of the BOF jar files, for example) do not affect actual measurements. It is also critical that you use the correct data to avoid (or not) caching at either the database layer (the Oracle buffer cache, for example) or the storage array layer (the vmax cache, for example). For example, you can search for one keyword during warm-up and another when collecting traces. This way, your results are unlikely to be in the database or storage layer cache, unless you want to test response times when data is cached at these layers. Turn on DFC trace — Turn on the DFC trace file collection by setting the following in dfc.properties file: # tracing dfc.tracing.enable=true dfc.tracing.file_prefix=dam_prefix dfc.tracing.include_rpcs=true dfc.tracing.include_session_id=true dfc.tracing.max_stack_depth=0 dfc.tracing.mode=compact dfc.tracing.timing_style=seconds dfc.tracing.verbose=true dfc.tracing.verbosity=verbose 72 EMC Documentum xCP 1.0 Performance Tuning Guide
Measuring Performance Execute the business transaction — After the log file (specified as dam_prefix in the preceding dfc.properties file) shows up in the logs directory, run your transaction. After completion of the transaction, turn off DFC tracing and make a copy of the trace file. Turn off DFC tracing — Turn off DFC tracing by disabling tracing, as shown in the following in dfc.properties file: # tracing dfc.tracing.enable=false dfc.tracing.file_prefix=dam_prefix dfc.tracing.include_rpcs=true dfc.tracing.include_session_id=true dfc.tracing.max_stack_depth=0 dfc.tracing.mode=compact dfc.tracing.timing_style=seconds dfc.tracing.verbose=true dfc.tracing.verbosity=verbose Determining RPC call source To determine the location of RPC calls, configure your \WEB- INF\classes\log4j.properties and dfc.properties files to have the stack trace of the call sent to the $DOCUMENTUM\log4j.log file as follows: 1. Turn on debugging in your log4.properties file as follows: Note: You can use the following listing for all your log4j settings. log4j.rootCategory=DEBUG, Console, File log4j.category.MUTE=OFF log4j.additivity.tracing=false log4j.appender.Console=org.apache.log4j.ConsoleAppender log4j.appender.Console.threshold=WARN log4j.appender.Console.layout=org.apache.log4j.PatternLayout log4j.appender.Console.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %m%n log4j.appender.File=org.apache.log4j.RollingFileAppender log4j.appender.File.File=C:/documentum/logs/log4j.log log4j.appender.File.MaxFileSize=100MB log4j.appender.File.layout=org.apache.log4j.PatternLayout log4j.appender.File.layout.ConversionPattern=%d{ABSOLUTE} %5p [%t] %m%n 2. Modify your dfc.properties file as follows: Note: A large max_stack_depth is not necessary. a. Update the application server dfc.properties file to enable tracing. b. Set the method_name_filter to match the method calls to be captured. c. Disable DEBUG messaging for the filter of interest by setting the log category to a string not configured for debugging in the log4j.properties file. For example: dfc.tracing.enable=true dfc.tracing.verbose=true EMC Documentum xCP 1.0 Performance Tuning Guide 73
Page 1 and 2:
EMC ® Documentum ® xCelerated Com
Page 3 and 4:
Table of Contents Preface .........
Page 5 and 6:
Table of Contents Configuring the B
Page 7 and 8:
Table of Contents List of Tables Ta
Page 9 and 10:
Preface This document addresses are
Page 11 and 12:
Overview Chapter 1 Creating the bes
Page 13 and 14:
Overview General guidelines Pay clo
Page 15 and 16:
Planning Capacity and Sizing Chapte
Page 17 and 18:
Planning Capacity and Sizing Planni
Page 19 and 20:
Planning Capacity and Sizing Load s
Page 21 and 22: Planning Capacity and Sizing Load s
Page 23 and 24: Planning Capacity and Sizing Begin
Page 25 and 26: Maximizing Process Throughput Chapt
Page 27 and 28: Maximizing Process Throughput Minim
Page 29 and 30: Maximizing Process Throughput Figur
Page 31 and 32: Maximizing Process Throughput Incre
Page 33 and 34: Maximizing Process Throughput High
Page 35 and 36: Chapter 4 Designing the Application
Page 37 and 38: Designing the Application Figure 10
Page 39 and 40: Designing the Application Note: Com
Page 45 and 46: Designing the Application Using sea
Page 47 and 48: Designing the Application Note: Add
Page 49 and 50: Designing the Application Rendering
Page 51 and 52: Designing the Application Changing
Page 53 and 54: Designing the Application Managing
Page 55 and 56: Designing Reports Chapter 5 This ch
Page 57 and 58: Designing Reports Planning and test
Page 59 and 60: Designing Reports missed report dat
Page 61 and 62: Designing Reports • Use database
Page 63 and 64: Configuring System Components Chapt
Page 65 and 66: Configuring System Components Figur
Page 67 and 68: Configuring System Components Figur
Page 69 and 70: Measuring Performance Chapter 7 Thi
Page 71: Measuring Performance Figure 27. Si
Page 75 and 76: Measuring Performance Analyzing lar
Page 77 and 78: Measuring Performance Figure 29. Re
Page 79 and 80: Measuring Performance [i.e]|[i.e]]
Page 81 and 82: Measuring Performance Figure 33. Sa
Page 83 and 84: Measuring Performance Analyzing mul
Page 85 and 86: Chapter 8 Maintaining the Repositor
Page 87 and 88: Maintaining the Repository and BAM
Page 89 and 90: Troubleshooting Chapter 9 This chap
Page 91 and 92: Troubleshooting Symptom BAM dashboa
Page 93 and 94: Index A activities consolidating, 2
Page 95 and 96: Index constraining, 49 latency and
Page 97: Index general guidelines, 49 get ne
show all

Performance Tuning Guide - EMC Community Network

Create successful ePaper yourself

Delete template?

Save as template?