Resolution:
Description:
============
Explanation of Java Monitoring (JMX) Parameters such as Avg DB Txn, Avg Cache Txn, PreRTC, InRTC, PostRTC, Cache hit probability, L1Cache hit ratio.

Environment:
==========
TIBCO BusinessEvents 3.x

Resolution:
==========
1). Avg DB Txn(millis) - The average time a database transaction (Insert/Update) takes to complete. It is obtained as Total time taken by all DB transactions/ Number of DB transactions. Also, it is valid cacheAside is used in the project.
                          

2). Avg Cache Txn(millis)  -The average time a cache transaction(Get/Put) takes to complete. It is obtained as Total time taken by all cache transactions/ Number of Cache transactions.                          
                          

3). PreRTC (millis) - Time taken before the thread enters the Rule. i.e., Time spent from the moment a message is received by BE until preprocessor function.
    
4). InRTC (millis) -  Time spent in a particular rule execution. i.e., Time spent after PreRTC and before PostRTC.
    
5). PostRTC (millis) -  Time spent in updating the cache and database as a result of the execution of data in Pre-processor and Rule.,  i.e., Time spent after after PreRTC and InRTC.
    
When an event arrives, the associated thread spends time at three stages as PreRTC,InRTC and PostRTC as explained above.
    

6). Cache hit probability -The chance of scoring a hit in the cache for querying the object.
    

7). L1Cache hit ratio - Hit ratio = Hit count / Total request count

The first time a request is made the object it is not in the cache. Hits - 0, Total =1

When requesting the object in the next Continue.process  cycle, Hits = 1, Total = 2
    
Continuing on... Hits = 2, Total = 3
              Hits = 3, Total = 4
              Hits = 4, Total = 5

The Hit ratio will start from 50%, 63%, 75%, 80%, 83%, 92.3 (=12/13) and so on until it hovers around 95.xxx%.