CloudTran Home

 
  
<< Back Contents  >  9.  Monitoring Cloudtran-Coherence Transactions Forward >>

9.2 Operation Timers

Operation timers collect statistics and feed them into the logs every few seconds. The original ones are obsolete, and you should switch on optimer2 using the switch in the isolator, manager and/or client application to get the relevant information reported

-DOpTimer2.on=true

Unlike with the screens, you only get information about a particular node rather than an aggregation across managers or an overall look at how the cluster is behaving. The data should be output every 5 seconds.

Typically, operations called across the network may be shown either from the point of view of the caller, so including the network time, or from the called node. Times referred to as "Invoke" are from the calling node, and "process" are from the called node.

 9.2.1  Operation Timer Data Shown in the Isolator Logfile
 9.2.2  Operation Timer Data Shown in the Manager Logfile
 9.2.3  Operation Timer Data Shown in the Client Logfile

9.2.1  Operation Timer Data Shown in the Isolator Logfile

The data reported is in the following format:

12:01:53.855.301 timers:   Completed  T:Avg_ms   T:Min(ms) T:Max(ms)    T:Tot(ms)  Pending  # Items Items:Max
 M2I_AGG_RQST_PROCESS            955     0.017      0.004      0.096       16.178        0     3577       16

  • M2I_AGG_RQST_PROCESS: This is the time for isolator request as seen by the isolator.


9.2.2  Operation Timer Data Shown in the Manager Logfile

The data reported is in the following format:

11:55:32.631.886 timers:   Completed  T:Avg_ms   T:Min(ms) T:Max(ms)    T:Tot(ms)  Pending  # Items Items:Max
 START_PROCESS                   636     0.042      0.000      1.100       26.923        0  
 COMMIT_PROCESS                  634     5.061      0.000     37.108    3,208.929        2  
 COMMIT_PART_0                   636     0.454      0.000     16.479      288.667        0  
 PUT_FLUSH_INFO                  636     0.386      0.000      2.057      245.299        0      888        5
 CONSTRUCT_TXIFP                 636     0.059      0.000      2.103       37.321        0  
 M2I_AGG_RQST_INVOKE             483     1.131      0.000     15.201      546.142        0     1524       30
 WRITE_DTXINFO_COMMIT_1          636     0.337      0.000      5.278      214.350        0  
 WRITE_DTXINFO_COMMIT_2          636     0.361      0.000      2.242      229.629        0  
 WRITE_DTXINFO_COMPLETE          625     0.373      0.000      5.115      232.991        0  
 DISTCOMMITABORT_INVOKE          636     0.003      0.000      0.121        2.031        0  
 DISTCOMMITABORT_PROCESS         888     0.119      0.000      0.936      106.005        0  
 PERSIST                         338    49.055     31.126     86.947   16,580.446        7      873       25
 DB_TRANSACTION                  338    48.603      0.000     86.809   16,427.873        6      873       25
 PARALLEL_EXECUTOR_ALLOC         888     0.010      0.000      1.325        8.992        0  

  • START_PROCESS: the time taken by the manager to start a transaction
  • COMMIT_PROCESS: the time taken by the manager to commit a transaction
  • COMMIT_PART_0: the time taken by the manager to commit the first part of the transaction
  • PUT_FLUSH_INFO: the time taken by the manager to put the transaction data into the cache
  • CONSTRUCT_TXIFP: the time taken to create the transaction status information
  • M2I_AGG_RQST_INVOKE: the time taken to request transaction clearance from the Isolator
  • WRITE_DTXINFO_COMMIT_1: the time taken to write the first part of the distributed transaction information
  • WRITE_DTXINFO_COMMIT_2: the time taken to write the second part of the distributed transaction information
  • WRITE_DTXINFO_COMPLETE: the time taken to complete the distributed transaction information
  • DISTCOMMITABORT_INVOKE: the time taken to call on all the managers involved in a transaction as seen from the coordinating manager
  • DISTCOMMITABORT_PROCESS: the time taken to process the distributed transaction as seen from the subordinate manager
  • PERSIST: the time taken to persist a transaction
  • DB_TRANSACTION: the time taken to commit the transaction on the database. This may be aggregated in a send with other transactions, if that is more efficient, and so won't necessarily relate to the persist figure directly.


9.2.3  Operation Timer Data Shown in the Client Logfile

The data produced is in the following format:

11:47:31.138.248 timers:   Completed  T:Avg_ms   T:Min(ms) T:Max(ms)    T:Tot(ms)  Pending  # Items Items:Max
 START_INVOKE                   1288     0.352      0.298      8.398      453.985        0  
 COMMIT_INVOKE                  1288     3.381      1.131     10.100    4,354.531        2  
 PARALLEL_EXECUTOR_ALLOC        1288     0.002      0.001      0.003        2.015        0  

As with the screens,

  • Start_Invoke is the length of time it takes for the client to start a tranaction.
  • Commit_Invoke is the time it takes for a transaction to be committed as seen from the client.

Copyright (c) 2008-2013 CloudTran Inc.