To enable Performance logging, you must have the <CapturePerformance> tags set to YES in _LogDirectives.txt. When enabled, the EZ begins capturing a single line of logging for each call received. The file is created with the date as part of the name, so there are only one of these logs per day that this logging option is enabled. The structure of the new log file is tab delimited with the following columns: DateTime, Operator, salespoint, TotalCallDuration, TotalSQLCallTime, TotalLoggingTime, FunctionName, ShortFunctionDetail, FullInvokeString. Here is a sample line:

 

 

This can easily be cut and pasted into Excel – the tabs separate the data into proper columns – allowing you to make subtotals and averages easily. In this sample line, we see that the operator ADMIN and salespoint RESERV made a SQLPASSTHROUGH call that lasted for 26 milliseconds (ms). 7 ms of the 26 were spent waiting for SQL Server and 1ms was spent logging.

If TruncatePerformanceLogLines is NO or omitted (recommended setting), the full invoke call is placed into the log. This can be used to feed a load testing setup and simulate all the captured activity. We are hopeful that this lightweight log gives a clearer picture of what servers are waiting for when they are stressed under load.

 

Note: EZ in the previous text above always refers to BookEZ, RentEZ, SalesEZ and TallyEZ applications.