Result Report - EcoSys - Customization & Programming - Hexagon

EcoSys Gateway Web Service API Client

Language
English
Product
EcoSys
Search by Category
Customization & Programming
EcoSys Version
9.0

The #END log event outputs the result report with record counts and performance details. The specific details vary slightly based on whether the operation is a data write, a data read, or an event trigger.

Example of data write result:

2014-03-01 15:22:02.659 [2876@localhost] #END "update" for "SampleAPI"

RECORDS:

Records Success/Sent : 297/300 (99.0%)

Records Per Second : 22.53

Web Service Overhead : 18.8%

Messages Sent : 8

TIMINGS:

Total Elapsed Seconds : 13.31 (0.22 min)

Server Elapsed Seconds : 10.81

Server CPU Seconds : 4.76

Server DB Seconds : 6.1

Notes on key report values

Success Percent: For object writes, check these values to verify that all records were accepted by the server.

Web Service Overhead: The amount of time elapsed that was not spent by the server processing the data. This includes any time spent sending and receiving data, formatting and parsing XML, and logging. It approximates the overhead incurred by utilizing the web service, separate from the work done by the server to process the data once received.

Records Per Second: This is the key performance metric that identifies the throughput of the system with respect to the specific API and data given. Varying the message size may improve this value, as well as tuning the configuration and the infrastructure.

Server Seconds: These values are captured by the server (process metrics), and aggregated across all messages. They can provide a high level picture of the resources consumed on the server side to process the data. The CPU and database values may exceed the elapsed time if parallelization is enabled.

For more informations on performance of API calls, look for the corresponding PROCESS METRICS log events in the EcoSys application log. These reports are available for every API call and includes detailed breakdown of resources and timing for each execution step.

When operating in JDBC mode, the output performance report from EcoSys Gateway will also include timing data about the SQL data source query performance.