Indicates the total number of XQuery plans currently cached in memory. A query with a cached plan does not require query compilation the next time it is run. For example, if you have 10 stored queries and of these you have executed only two queries (one or more times each), then the query cache will have the following entries:
If logging is enabled on your WebLogic Server installation, the server log files contain information about the time spent to compile and execute a query. For more information, see Server Log in the WebLogic Server documentation
Custom applications can contain debugging calls to
stdout that record times when Liquid Data compiles a query, submits the query to a data source for processing, receives the results from the data source, and processes the results. For more information, see Using WebLogic Logging Services.
You can use the WebLogic Server Administration Console to monitor the health and performance of the domain in which WebLogic is deployed, including such resources as servers, JDBC connection pools, JCA, HTTP, the JTA subsystem, JNDI, and EJBs. For more information, see Monitoring a WebLogic Server Domain in Configuring and Managing WebLogic Server.
You can use performance monitoring tools, such as the OptimizeIt and JProbe profilers, to identify Liquid Data application hot spots that result in either high CPU utilization or high contention for shared resources. For more information, see Tuning WebLogic Server Applications. For a complete list of performance monitoring resources, see Related Reading in WebLogic Server Performance and Tuning.