The benchmark logs are an extension of the transaction logs - providing deeper analysis of the query transactions for optimization purposes.
Note that Benchmark logging is disabled by default. Go to The Settings > Logging to enable this feature.
Beware: Benchmarking logging can significantly slow the performance of the platform. They should be turned on for diagnostics only and then turned off.
The benchmark log page is broken into 2 panels.
The top panel shows a summary of all transactions by the target data source (server), the Pyramid processing server (run time engine); the database type that was queried and its name; the user and time stamp of the transaction.
The bottom panel shows specifics for any selected transaction, showing each stage in the query pipeline.
- The graphic on the left is used to summarize the times and give a bird's eye view of the pipeline. The graphic is very useful in diagnosing performance issues and separating out Pyramid processing from database processing from network latency.
- Pyramid Time represents the time allotted to Pyramid processing on the server (pre and post) and the Pyramid web client
- Network represents the time taken to send and receive data across the network between the client and server
- Query Time represents the time taken to connect to a data source, submit the request, for the data source to process the request and return a response to Pyramid.
- The rows and columns provide metrics on the size of the result.
- The grid on the left highlights each stage and the time taken to resolve each element in the pipeline from client to server, to database and back to client.
It is beyond the scope of this help article to explain each item. These details are for Pyramid engineers when trying to diagnose performance issues for a customer.
If benchmark logging is enabled, the benchmark summary graphic is also available from the "App Tab" in the full client interface.