Performance Tuning Guide - EMC Community Network

More documents

Recommendations

Info

Designing the Application Figure 13. Hiding a process variable Converting simple process variables to SDTs If your design makes extensive use of simple process variables and you can use SDTs instead, create new SDTs with attributes that map to the previously used simple process variables. Replace as many process variables as possible with SDT attributes. Performance improves even if you consolidate the simple process variables into several (instead of only one) SDTs. After creating the SDT, delete the simple process variables for which the SDT provides an attribute. If your application is already in production and you cannot consolidate simple process variables into SDTs, hide those simple process variables that do not show up in any forms (Hiding unused variables, page 39) If there are many process variables that are mandatory on the form because they are mapped to a field and the application is in production and cannot be changed, create a workflow template you can use while migrating off the old template. Chapter 5, Designing Reports provides information on the potential performance impact of updating the BAM database with an SDT definition. Minimizing form size Form size determines form rendering performance more than any other single factor. To maximize form rendering performance, consider the following: • Only use packages when necessary. • Adaptor-based data increases form footprint and affects response time (Using adaptors, page 52). • Use virtual documents or embedded folders, instead of tabs, to contain the forms or documents needed for processing. Form size impacts system sizing. A typical JVM can support anywhere between 40-200 users, depending on the size of the forms involved in day to day business activities. The larger the forms, the fewer users the JVM can support. 40 EMC Documentum xCP 1.0 Performance Tuning Guide
Designing the Application Figure 14, page 41 provides an example of a large form with the following characteristics: • 46 packages (3 visible) • 20 fields mapping • two embedded folders • four additional tabs • 30 adaptors. Figure 14. Sample form Figure 14, page 41 represents a form that takes up 10 MB of heap space. In this case, a 1024 MB heap can only support about 80 users. The following breaks down the form components making up the 10 MB form size: • Packages: 43 packages marked as visible add 2 MB per form instance in the JVM. For example, 200 users opening up this form consume 400 MB in the JVM. To minimize this impact, mark only the packages you need as visible. Set the rest to invisible. • Forms Template: The DOM object created internally for this type of form composition consumes roughly 2 MB per instance. EMC Documentum xCP 1.0 Performance Tuning Guide 41
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: Designing the Application Note: Com
Page 43 and 44: Designing the Application Figure 15
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 and 72: Measuring Performance Figure 27. Si
Page 73 and 74: Measuring Performance Execute the b
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?