Hybris Flexible Query Cache Test
The SAP Hybris comes with Flexible Query Cache which caches the result of each query that is run on the data source. The main advantage of this is that if the same query is executed again, the results can be served from cache rather than going back to database.
The purpose of this test is to monitor Flexible Query Cache on continuous basis for number of entries and fill ratio so that administrator get an advance insight if the cache is going to be full soon.
Target of the test : A SAP Hybris system
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for flexible query cache belonging to each tenant
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
The host for which the test is to be configured. |
Port |
Specify the port at which the specified host listens. By default, this is 9002. |
JMX Remote Port |
Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the JMX remote port number of the SAP Hybris monitoring application. The default is 12002. |
JNDI Name |
The JNDIname is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same. |
JMX User and JMX Password |
If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. |
Confirm Password |
Confirm the password by retyping it here. |
Provider |
This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the Provider as value “default”. |
Timeout |
Specify the duration (in seconds) for which this test should wait for a response from the target Java application. If there is no response from the target beyond the configured duration, the test will timeout. By default, this is set to 1000 seconds if the Mode is JMX |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Current entries |
Indicates the total number of entries in cache during the last measurement period. |
Number |
If the cache fill ratio is towards 100%, it may be a sign that either the cache size is too small for the transactions it is supporting or there is some issue with cache invalidation and eviction algorithm.
|
Current entries percentage |
Indicates the numbed of entries in the last measurement period against maximum entries in the cache. |
Percentage |
|
Maximum Entries |
Indicates the maximum number of entries allowed in the entity region cache. |
Number |