Performance Tuning Documentum Web Based Applications - EMC ...

More documents

Recommendations

Info

8Hardware changes - Adding CPUs or changing the I/O subsystem configurationDatabase configuration - Changing initialization parameter settingsSchema changes - Hash partitioning a table or index, or using automatic segment-spacemanagement (ASSM)Application changes - Using the cache option for sequences or using bind variablesUsing other advisors - Running the SQL Tuning Advisor on high load SQL or running theSegment Advisor on hot objectsReports provided by ADDM1. CPU Utilization2. Average Active Sessions3. Disk I/O4. Instance ThroughputOther Important Features
91. Running the SQL Tuning Advisor on high-load SQL statements or running the SegmentAdvisor on hot objects. Documentum provides the description of how to use it.(Please referthe resources section).2. Automatic Workload Repository (AWR)Database statistics provide information about the type of load on the database and the internaland external resources used by the database. To accurately diagnose performance problemswith the database using ADDM, statistics must be available.Oracle Database generates manytypes of cumulative statistics for the system, sessions, and individual SQL statements. OracleDatabase also tracks cumulative statistics about segments and services. The AutomaticWorkload Repository (AWR) automates database statistics gathering by collecting, processing,and maintaining performance statistics for database problem detection and self-tuning purposes.The database statistics collected and processed by AWR include:Time Model StatisticsTime model statistics are statistics that measure the time spent in the database by operation type.Wait Event StatisticsWait events are statistics that are incremented by a session to indicate that it had to wait for anevent to complete before being able to continue processing. Wait event data reveals varioussymptoms of problems that might be impacting performance, such as latch contention, buffercontention, and I/O contention.Session and System StatisticsA large number of cumulative database statistics are available on a system and session level.Active Session History StatisticsThe Active Session History (ASH) statistics are samples of session activity in the database.Active sessions are sampled every second, and are stored in a circular buffer in the systemglobal area (SGA). Any session that is connected to the database and using CPU, or is waitingfor an event that does not belong to the idle wait class, is considered an active session. Bycapturing only active sessions, a manageable set of data is represented with the size beingdirectly related to the work being performed, rather than the number of sessions allowed on thesystem.High-Load SQL StatisticsSQL statements that are consuming the most resources produce the highest load on the system,based on criteria such as elapsed time and CPU time.Java Management Extension (JMX) and J2SE 5.0The JMX specification defines architecture, the design patterns, the APIs, and the services forapplication and network management and monitoring in the Java programming language.
Page 1 and 2: Performance Tuning Documentum Web B
Page 3 and 4: 3Few words about myselfI having bee
Page 5 and 6: 5Load Testing ApproachThis turns ou
Page 7: 7Diagram showing DB TimeThe types o
Page 11: 11ConclusionPerformance Tuning Docu

Performance Tuning Documentum Web Based Applications - EMC ...

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

Delete template?

Save as template?