Choose a topic

• 25.2.1 Task 1: Enable the Exalogic Automated TunerAutomated tuning is an optimization that allows applications to automatically tune JPA and session configuration for a specific purpose. Automated tuning facilitates a one-flag configuration option for configuring multiple settings or for performing dynamic tuning. The use of automated tuning in micro-benchmark tests that contained a mix of insert updates and reads showed a reduction in CPU (both on the middle tier and database tier) and a reduction in memory usage. The use of automated tuning in CRUD and query micro-benchmark tests showed an increase in performance against tests that did not use the optimization. For details about automated tuning, see "Automated Tuning".TopLink includes an automated tuner that provides an optimized configuration for the Exalogic platform. It enables multiple performance features and enables an Exalogic-specific profiler. The profiler monitors the startup phase of the application and detects queries that trigger the n+1 query execution problem. It then optimizes these queries to use batch fetching. For dynamic queries that cannot use batch fetching, it further analyses these queries and defines a runtime state machine to detect and optimize these queries. For details about profilers, see "Performance Optimization Recommendations and Tips".When using the Exalogic tuner, the following persistence unit properties are set prior to deployment:Note:If a property is explicitly set (such as in the persistence.xml file), then it takes precedence over the properties that are automatically set by the Exalogic tuner.WEAVING_EAGER = trueCACHE_SIZE_DEFAULT = 1000QUERY_CACHE = trueORDER_UPDATES = trueBATCH_WRITING = JDBCPERSISTENCE_CONTEXT_CLOSE_ON_COMMIT = truePERSISTENCE_CONTEXT_FLUSH_MODE = CommitDDL_GENERATION_INDEX_FOREIGN_KEYS = truePROFILER = oracle.toplink.exalogic.tuning.TuningAgentFREE_METADATA = trueIf connection pooling is used, then statement caching for the session is automatically enabled. In addition, after deploying and connecting to the session, the Exalogic tuner automatically sets the session to use the Exalogic-specific DynamicParameterizedHybridBatchWritingMechanism batch writer. For details about batch writing, see "Task 4: Configure Heterogeneous Batch Writing on Exalogic".To enable the Exalogic tuner, specify ExaLogic as the value of the eclipselink.tuning property in the persistence.xml file. For example:On Oracle WebLogic Server, the Exalogic automated tuner can be enabled with the console using the domain Configuration | General tab and selecting the Enable Exalogic Optimizations option, or it can be enabled through the DomainMBean.ExalogicOptimizationsEnabled MBean attribute.
• 25.2.1 Task 1: Enable the Exalogic Automated TunerAutomated tuning is an optimization that allows applications to automatically tune JPA and session configuration for a specific purpose. Automated tuning facilitates a one-flag configuration option for configuring multiple settings or for performing dynamic tuning. The use of automated tuning in micro-benchmark tests that contained a mix of insert updates and reads showed a reduction in CPU (both on the middle tier and database tier) and a reduction in memory usage. The use of automated tuning in CRUD and query micro-benchmark tests showed an increase in performance against tests that did not use the optimization. For details about automated tuning, see "Automated Tuning".TopLink includes an automated tuner that provides an optimized configuration for the Exalogic platform. It enables multiple performance features and enables an Exalogic-specific profiler. The profiler monitors the startup phase of the application and detects queries that trigger the n+1 query execution problem. It then optimizes these queries to use batch fetching. For dynamic queries that cannot use batch fetching, it further analyses these queries and defines a runtime state machine to detect and optimize these queries. For details about profilers, see "Performance Optimization Recommendations and Tips".When using the Exalogic tuner, the following persistence unit properties are set prior to deployment:Note:If a property is explicitly set (such as in the persistence.xml file), then it takes precedence over the properties that are automatically set by the Exalogic tuner.WEAVING_EAGER = trueCACHE_SIZE_DEFAULT = 1000QUERY_CACHE = trueORDER_UPDATES = trueBATCH_WRITING = JDBCPERSISTENCE_CONTEXT_CLOSE_ON_COMMIT = truePERSISTENCE_CONTEXT_FLUSH_MODE = CommitDDL_GENERATION_INDEX_FOREIGN_KEYS = truePROFILER = oracle.toplink.exalogic.tuning.TuningAgentFREE_METADATA = trueIf connection pooling is used, then statement caching for the session is automatically enabled. In addition, after deploying and connecting to the session, the Exalogic tuner automatically sets the session to use the Exalogic-specific DynamicParameterizedHybridBatchWritingMechanism batch writer. For details about batch writing, see "Task 4: Configure Heterogeneous Batch Writing on Exalogic".To enable the Exalogic tuner, specify ExaLogic as the value of the eclipselink.tuning property in the persistence.xml file. For example:On Oracle WebLogic Server, the Exalogic automated tuner can be enabled with the console using the domain Configuration | General tab and selecting the Enable Exalogic Optimizations option, or it can be enabled through the DomainMBean.ExalogicOptimizationsEnabled MBean attribute.