You can set srp_timestamp fields to measure the time taken (in microseconds) for each transaction processing step, as detailed below:

• srp_timestamp_1 – MQ wait time: For queue connectors, this is the time between the MQ put and the time that the ODE reads the transaction. The time will be 0 if the transaction comes in via a socket connector.
• srp_timestamp_2 – Execution wait time: The time between when the transaction is received and an engine thread is available to pick up the transaction for processing. This time can be inflated if another step holds up the engine threads.
• srp_timestamp_3 – Execution prep time: The time to execute the prepareTRX bean, which adds the system segments and initial values to the transaction to begin processing.
• srp_timestamp_4 – MEH key resolve time: The time to execute the model’s resolve keys macro and set the MEH lookup key values.
• srp_timestamp_5 – MEH fetch time: The time spent getting all of the required variable segments. This value includes the time to get the segments from the MEH database and any time that was spent waiting on other threads due to contention.
• srp_timestamp_6 – Rules/Model processing time: The time spent processing the transaction through the rule and model code in the SAS sessions.
• srp_timestamp_9 – Total processing time: The total time ODE took to receive, process the transaction, and send a response back. This value does not include the post score action.
• srp_timestamp_11 - Transaction Model (Python): The time spent processing the transaction through the Python model.
• srp_timestamp_12 - MEH key resolve time (Python): The time ODE spent to resolve MEH keys for the transaction (Python).

To enable logging of additional transaction srp_timestamps, add the srp_timestamps of interest under the bean with the following bean_id in the actions.xml file. By enabling this logging configuration, log messages will be printed only if the transaction exceeds the SLA_NOTICE time defined in ose.properties. (Note: Here is a txt file with the SRP timestamps.)

Note: The recording of srp_timestamps has little to no adverse effect on system performance.