Microservices Runtime Service Cache Test

The function of service cache in webMethods Microservices Runtime is to optimize performance by storing the results of service executions so that when a service is called again with the same input values, the cached results are returned instead of executing the service again. This reduces the response time and decreases the load on the system by avoiding repeated processing. This test helps the administrators to track key metrics such as cache hit and miss ratios, which indicate how efficiently the cache is serving repeated requests. A high cache hit ratio improves response times and reduces backend load, while a high miss ratio may indicate the need for cache tuning or potential issues in service execution.

Target of the test : webMethods Microservices Runtime

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each service in the target webMethods Microservices Runtime server.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the target for which the test is to be configured.
Port	The port number at which the specified target listens to. By default, this will be 5555.
User and Password	Specify the credentials of a user who has the right to execute API commands on the target and pull out metrics. The specified user is the User who should possess Administator privileges and should be associated with the Logon as a Service policy.
Confirm Password	Confirm the password by retyping it here.
SSL	Set this flag to Yes, if the target being monitored is SSL-enabled.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Service executions	Indicates the number of executions encountered by this service.	Number
Concurrent service executions	Indicates the number of concurrent executions encountered by this service.	Number
Cache hits	Indicates the number of cache hits encountered by this service.	Number
Cache hit ratio	Indicates the percentage of cache hit ratio for this service.	Percent	A higher value of this measure is desired. This means more requests are served directly from the cache, leading to faster response times and reduced load on backend services. Typically, a cache hit ratio of 80% or higher is considered good, especially for microservices where repeated calls with the same inputs can be cached efficiently. However, it is important to balance a high cache hit ratio with data freshness to avoid serving outdated information.
Cache miss ratio	Indicates the percentage of cache miss ratio for this service.	Percent	In webMethods Microservices Runtime, the cache miss ratio should not be more; ideally, it should be low. A cache miss happens when a requested piece of data is not found in the cache, which requires the system to fetch the data from the underlying source, resulting in slower performance. Minimizing cache misses is important for maintaining efficiency and performance in the microservices environment.
Active cache entries	Indicates the number of active cache hits encountered by this service.	Number
Expired cache entries	Indicates the number of expired cache hits encountered by this service.	Number
Prefetches	Indicates the number of prefetches encountered by this service.	Number
Service errors	Indicates the number of errors encountered by this service.	Number