Understanding DMS Event Output
6.8 DMS Best Practices
The use of DMS metrics can have an impact on application performance. When adding metrics, consider the following: ■ Use a High Resolution Clock to increase DMS Precision By default DMS uses the system clock for measuring time intervals during a PhaseEvent. The default clock reports microsecond precision in C processes such as Apache and reports millisecond precision in Java processes. Optionally, DMS supports a high resolution clock to increase the precision of performance measurements and lets you select the values for reporting time intervals. You can use a high resolution clock when you need to time phase events more accurately than is possible using the default clock or when the systems default clock does not provide the resolution needed for your requirements. System clocks are not necessarily as accurate as their precision implies. For example, a system clock that reports time in milliseconds may not tick change once per millisecond. Instead, it may take up to 15ms to tick as shown in the following example: Table 6–10 shows a phase with a 12ms duration that runs from actual time 12:00:00.002 to 12:00:00.014 would be calculated in system time as having a duration of zero. Similarly, a phase with a 2ms duration running from 12:00:00.014 to 12:00:00.016 would be reported in system time as having a duration of 15ms. ■ Configure DMS Clocks for Reporting Time for Java Execution Context - - - Yes Yes - Http Request - - - Yes Yes - Table 6–10 Default System Clock Time versus Actual Time in milliseconds Actual Time System Time 12:00:00.000 12:00:00.000 12:00:00.001 12:00:00.000 12:00:00.002 12:00:00.000 [...] 12:00:00.014 12:00:00.000 12:00:00.015 12:00:00.015 12:00:00.016 12:00:00.015 Note: These behaviors are more evident on some operating systems than others. Use caution when analyzing individual periods of time that are shorter than the tick period of the system clock. Configuring DMS to use a higher resolution clock will cause DMS to record phase sensor activations with higher resolution, but the accuracy will still be limited by the underlying system. Table 6–9 Cont. Actions Performed on Source Object Types Create Update Delete Start Stop Abort Oracle Dynamic Monitoring Service 6-29 Selecting the high resolution clock changes clocks for all applications running on the server where the clock is changed. You set the DMS clock and the reporting values globally using the oracle.dms.clock and oracle.dms.clock.units properties, which control process startup options. For example, to use the high resolution clock with the default values, set the following property on the Java command line: -Doracle.dms.clock=highres Table 6–11 shows supported values for the oracle.dms.clock property. Table 6–12 shows supported values for the oracle.dms.clock.units property. Note the following when using the high resolution DMS clock: ■ When you set the oracle.dms.clock and the oracle.dms.clock.units properties, any combination of upper and lower case characters is valid for the value that you select case is not significant. For example, any of the following values are valid to select the high resolution clock: highres, HIGHRES, HighRes. ■ DMS checks the property values at startup. When the clock property is set with a value not listed in Table 6–11 , DMS uses the default clock. If the oracle.dms.clock property is not set, DMS uses the default clock. Caution: If you use the high resolution clock, the default values are different from the value that Fusion Middleware Control expects msecs. If you need the Fusion Middleware Control displays to be correct when using the high resolution clock, then you need to set the units property as follows: -Doracle.dms.clock.units=msecs Table 6–11 oracle.dms.clock Property Values Value Description DEFAULT Specifies that DMS use the default clock. With the default clock, DMS uses the Java call java.lang.System.currentTimeMillis to obtain times for PhaseEvents. The default value for the units for the default clock is MSECS. HIGHRES The Java Highres clock uses System.nanoTime no JNI required. Table 6–12 oracle.dms.clock.units Property Values Value Description MSECS Specifies that the time be converted to milliseconds and reported as msecs. A millisecond is 10 -3 seconds. Note : This is the default value for the default clock. USECS Specifies that the time be converted to microseconds and reported as usecs. A microsecond is 10 -6 seconds. NSECS Specifies that the time be converted to nanoseconds and reported as nsecs. A nanosecond is 10 -9 seconds. Note : This is the default value for the high resolution clock. 6-30 Oracle Fusion Middleware Performance and Tuning Guide ■ When the clock units property is set to a value not listed in Table 6–12 , DMS uses the default units for the specified clock. 7 Oracle Metadata Service MDS Performance Tuning 7-1 7 Oracle Metadata Service MDS Performance Tuning This chapter provides tuning tips for Oracle Metadata Service MDS. ■ Section 7.1, About Oracle Metadata Services MDS ■ Section 7.2, Tuning Database Repository ■ Section 7.3, Purging Document Version History ■ Section 7.4, Using Database Polling Interval for Change Detection ■ Section 7.5, Tuning Cache Configuration ■ Section 7.6, Analyzing Performance Impact from Customization ■ Section 7.7, Understanding DMS metrics and Characteristics7.1 About Oracle Metadata Services MDS
Oracle Metadata Services MDS is an application server and Oracle relational database that keeps metadata in these areas: a file-based repository data, dictionary tables accessed by built-in functions and a metadata registry. One of the primary uses of MDS is to store customizations and persisted personalization for Oracle applications. Oracle Metadata Services MDS is used by components such as Oracle WebCenter Framework and Oracle Application Development Framework ADF to manage metadata. Examples of metadata objects managed by MDS are: JSP pages and page fragments, ADF page definitions and task flows, and customized variants of those objects.7.2 Tuning Database Repository
For optimal performance of MDS APIs, the database schema for the MDS repository must be monitored and tuned by the database administrator. This section lists some recommended actions to tune the database repository: ■ Collect Schema Statistics ■ Increase Redo Log Size ■ Reclaim Disk Space Note: Most of the Oracle Metadata Service configuration parameters are immutable and cannot be changed at run time unless otherwise specified.Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to this Document
» Related Documentation Oracle Fusion Middleware Online Documentation Library
» About Identifying Top Performance Areas
» Ensure the Hardware Resources are Sufficient
» Selecting a Garbage Collection Scheme
» Disabling Explicit Garbage Collection
» Logging Low Memory Conditions
» Monitoring and Profiling the JVM
» Initialization Parameters for Oracle 10g
» Initialization Parameters for Oracle 11g
» Tuning Redo Logs Location and Sizing
» Automatic Segment-Space Management ASSM
» Reuse Database Connections Oracle Fusion Middleware Online Documentation Library
» Enable Data Source Statement Caching
» MaxClientsThreadsPerChild HTTP Connection Limits
» Setting the Maximum Number of Connections for Data Sources Tuning the WebLogic Sever Thread Pool
» Tuning Oracle WebCenter Concurrency
» Tuning BPEL Concurrency Control Concurrency
» Set Logging Levels Oracle Fusion Middleware Online Documentation Library
» About Oracle Fusion Middleware Performance Planning
» Define Operational Requirements Identify Performance Goals
» Understand User Expectations Define Your Performance Objectives
» Conduct Performance Evaluations Define Your Performance Objectives
» Design Applications for Performance and Scalability
» Monitor and Measure Your Performance Metrics
» Measuring Your Performance Metrics
» Viewing Performance Metrics Using Fusion Middleware Control
» Oracle WebLogic Server Administration Console
» WebLogic Diagnostics Framework WLDF
» Viewing Performance Metrics Using the Spy Servlet
» Oracle Process Manager and Notification Server Oracle Enterprise Manager 11g Grid Control
» Native Operating System Performance Commands Network Performance Monitoring Tools
» How Persistent Connections Can Reduce Httpd Process Availability
» Access Logging Oracle HTTP Server Logging Options
» Configuring the HostNameLookups Directive
» Error logging Oracle HTTP Server Logging Options
» Oracle HTTP Server SSL Caching
» SSL Application Level Data Encryption SSL Performance Recommendations
» Oracle HTTP Server Port Tunneling Performance Issues
» Analyze Static Versus Dynamic Requests
» Beware of a Single Data Point Yielding Misleading Results
» Beware of Having More Modules
» Monitoring Oracle HTTP Server
» DMS Nouns Common DMS Terms and Concepts
» DMS Sensors Common DMS Terms and Concepts
» DMS Availability Oracle Fusion Middleware Online Documentation Library
» DMS Architecture Overview Oracle Fusion Middleware Online Documentation Library
» Viewing Metrics Using the Spy Servlet
» Viewing metrics with JConsole
» Accessing DMS Metrics with WLDF
» DMS Execution Requests and Sub-Tasks
» DMS Execution Context Communication
» Adding and Editing Destinations
» Adding and Editing Event Routes
» Compound Operations Configuring the DMS Event System
» MBean Creator Destination HTTP Request Tracker Destination JRockit Flight Recorder Destination
» Understanding DMS Event Output
» Understanding DMS Event Actions
» DMS Best Practices Oracle Fusion Middleware Online Documentation Library
» About Oracle Metadata Services MDS
» Reclaim Disk Space Monitor the Database Performance
» Using Database Polling Interval for Change Detection
» Document Cache Tuning Cache Configuration
» Analyzing Performance Impact from Customization
» Understanding DMS metrics and Characteristics
» About Oracle ADF Oracle Fusion Middleware Online Documentation Library
» Oracle ADF Faces Configuration and Profiling
» Performance Considerations for ADF Faces
» Tuning ADF Faces Component Attributes
» Performance Considerations for Table and Tree Components
» Performance Considerations for autoSuggest
» Data Delivery - Lazy versus Immediate
» Performance Considerations for DVT Components
» Creating View Objects View Objects Tuning
» Configuring View Object Data Fetching
» Additional View Object Configurations
» Batch Processing ADF Server Performance
» General AM Pool Configurations
» AM Pool Sizing Configurations
» AM Pool Resource Cleanup Configurations
» ADFc: Region Usage ADF Server Performance
» Reusing Static Data ADF Server Performance
» Conditional Validations ADF Server Performance
» About Oracle TopLink and EclipseLink
» Entity Relationships Query Parameter Tuning
» Cache Refreshing Scenarios Cache Configuration Tuning
» Locking Modes Cache Configuration Tuning
» Coherence Integration Oracle Fusion Middleware Online Documentation Library
» Mapping and Descriptor Configurations
» Analyzing EclipseLink JPA Entity Performance
» Hardware Resources Optimizing Hardware Resources
» Configuring WebCache Memory Memory Configuration
» Network Bandwidth Optimizing Network Connections
» Network Connections Optimizing Network Connections
» Network-Related Parameters Optimizing Network Connections
» Optimizing Response Time Oracle Fusion Middleware Online Documentation Library
» Optimizing Performance with Oracle ADF
» About SOA Suite Configuration Properties
» Configuring Data Sources for SOA Weblogic Server Performance Tuning
» Modifying SOA Configuration Parameters JVM Tuning Parameters About Oracle Business Rules
» Use Java Beans Basic Tuning Considerations
» Assert Child Facts instead of Multiple Dereferences
» Avoid Side Affects in Rule Conditions
» Avoid Expensive Operations in Rule Conditions
» Consider Pattern Ordering Basic Tuning Considerations
» Consider the Ordering of Tests in Rule Conditions
» Use Functions Instead of AssertXPath and Supports XPath
» Dispatcher Invoke Threads BPEL Threading Model
» Dispatcher Engine Threads BPEL Threading Model
» Dispatcher System Threads BPEL Threading Model
» Dispatcher Maximum Request Depth
» Audit Level Basic Tuning Considerations
» AuditDetailThreshold Basic Tuning Considerations
» LargeDocumentThreshold Basic Tuning Considerations
» Validate XML Basic Tuning Considerations
» SyncMaxWaitTime Basic Tuning Considerations
» InstanceKeyBlockSize Basic Tuning Considerations
» Tables Impacted By Instance Data Growth
» About Oracle Mediator Oracle Fusion Middleware Online Documentation Library
» metricsLevel Basic Tuning Considerations
» Domain-Value Maps Basic Tuning Considerations
» Deferred Routing Rules Basic Tuning Considerations
» Resequencer Basic Tuning Considerations
» Audit Level LargeDocumentThreshold Basic Tuning Considerations
» Dispatcher Engine Threads Basic Tuning Considerations
» Dispatcher Invoke Threads Basic Tuning Considerations
» Process Measurement Tuning Process Analytics
» Tuning Process Cubes Tuning Process Analytics
» Minimize Client Response Time
» Choose the Right Workflow Service Client
» Narrow Qualifying Tasks Using Precise Filters
» Retrieve Subset of Qualifying Tasks Paging
» Fetch Only the Information That Is Needed for a Qualifying Task
» Reduce the Number of Return Query Columns Use the Aggregate API for Charting Task Statistics
» Use the Count API Methods for Counting the Number of Tasks
» Create Indexes On Demand for Flexfields
» Use the doesTaskExist Method
» Archive Completed Instances Periodically
» Select the Appropriate Workflow Callback Functionality
» Minimize Performance Impacts from Notification
» Deploy Clustered Nodes Improving Server Performance
» Use Workflow Reports to Monitor Progress
» Specify Escalation Rules Completing Workflows Faster
» Specify User and Group Rules for Automated Assignment
» Use Task Views to Prioritize Work
» Tuning Identity Provider Oracle Fusion Middleware Online Documentation Library
» Tuning the Database Oracle Fusion Middleware Online Documentation Library
» About Oracle Adapters Oracle Fusion Middleware Online Documentation Library
» Inbound Throttling Best Practices
» Outbound Throttling Best Practices
» Outbound Performance Best Practices
» JCA Adapter Basic Tuning Considerations
» Existence Checking Oracle JCA Adapter for Database Tuning
» adapter.jms.receive.threads Property
» Oracle Socket Adapter Tuning Oracle MQ Adapter Tuning
» Tune the Active Data Retrieval Interval
» Message Batching Enterprise Message Source Tuning
» About Oracle Business Activity Monitoring About Oracle User Messaging Services
» SMPP Driver Performance Tuning
» Email Driver Polling Frequency
» Database Tuning for Optimal Throughput
» MDS Cache Size Oracle Fusion Middleware Online Documentation Library
» Number of Threads Oracle Fusion Middleware Online Documentation Library
» JMS Multiple Out Queues Setting
» Design Time Considerations for Proxy Applications
» Design Considerations for XQuery Tuning
» About Oracle Internet Directory
» Introduction to Tuning Oracle Internet Directory
» Database Parameters Basic Tuning Considerations
» LDAP Server Attributes Basic Tuning Considerations
» Database Statistics Basic Tuning Considerations
» Replication or Oracle Directory Integration Platform Replication Server Configuration
» Garbage Collection Configuration Advanced Configurations
» Oracle Internet Directory with Oracle RAC Database
» Password Policies and Verifier Profiles
» Values for Configuring the Entry Cache
» Tuning Security Event Tracking
» Number of Entries to be Returned by a Search
» Timeout for Write Operations
» Bulk Load Operation Specific Use Cases
» Bulk Delete Operation Specific Use Cases
» High LDAP Write Operations Load
» Entry Cache Enabled Configuration
» Entry Cache Disabled Configuration.
» Optimizing Searches for Skewed Attributes
» Optimizing Performance of Complex Search Filters
» Updating Database Statistics by Using oidstats.sql
» Setting Performance-Related Replication Configuration Attributes
» Modifying Instance-Specific Attributes by Using Fusion Middleware Control
» Modifying Shared Attributes by Using Fusion Middleware Control
» Modifying Performance-Related Instance-Specific Configuration Entry Attributes
» About Oracle Virtual Directory Basic Tuning Considerations
» Database Adapters Advanced Tuning Configurations
» Join Adapters Advanced Tuning Configurations
» General Filter Tuning Advanced Tuning Configurations
» Load Balancer Local Store Adapter Tuning
» Cache Hit Logic Cache Plug-In Tuning
» Cache Plug-in Memory Management
» LDAP Listener Tuning Advanced Tuning Configurations
» Server Tuning Advanced Tuning Configurations
» Connection Pool Settings Connection Settings Federation Data Store Settings
» RDBMS Compression Database Tuning
» About Oracle Identity Federation Oracle HTTP Server Tuning
» SOAP Connections SAML Protocol Tuning
» XML Digital Signatures POST and Artifact Single Sign-On Profiles
» About Security Services Oracle Fusion Middleware Online Documentation Library
» OPSS PDP Service Tuning Parameters
» Policy Manager Oracle Web Services Security Tuning
» Configuring the Log Assertion to Record SOAP Messages
» Monitoring the Performance of Web Services
» Setting System Limit Setting JDBC Data Source
» Setting JRockit Virtual Machine JVM Arguments Using Content Compression to Reduce Downloads
» Setting HTTP Session Timeout Setting JSP Page Timeout
» Setting ADF Client State Token
» Setting ADF View State Compression
» Setting MDS Cache Size and Purge Rate Configuring Concurrency Management
» Tuning Performance of the Announcements Service
» Tuning Performance of the Discussions Service
» Tuning Performance of the Portlet Service
» Enabling Java Object Cache for WSRP Producers
» Suppressing Optimistic Rendering for WSRP Portlets
» Tuning Performance of Oracle PDK-Java Producers
» Setting ExcludedActionScopeRequestAttributes for Portlets
» Setting DefaultServedResourceRequiresWsrpRewrite for WSRP Portlets
» Setting DefaultProxiedResourceRequiresWsrpRewrite for WSRP Portlets
» Importing Consumer CSS Files in IFrame Portlets
» Configuring Portlet Timeout Tuning Portlet Configuration
» Tuning Performance of OmniPortlet
» Segregation of Network Traffic Segregation of Processes and Hardware Interrupt Handlers
» CPU Requirements Memory Requirements
Show more