Performance Metrics of Trial Balance Run

Last updated
Save as PDF

This article contains details of the performance metrics of a journal run.

Performance metrics calculation

Performance metrics calculation for the trial balance run is based on the duration of the longest subtask.

Performance metrics is calculated using the following formula:

Zuora Trial Balance Run Duration(in minutes) ≈ Max of (Number of transactions being processed / Average Transaction Processing Throughput)

Reports and their throughput

Different reports have different througputs.

Type	Transactions in the report	Throughput
AR Aging Report	Based on the Billing Account/Invoice/Debit Memo which has non zero balance as of accounting period end date	120,000/min
AR Detail Report	The billing transactions whose transaction date is in the accounting period	400,000/min
Revenue Detail Report	Based on revenue schedule which has recognized amount in and after the accounting period	400,000/min
Realized FX Gain Loss Report	Home currency is set; The payment, refund, credit memo whose transaction date is in the accounting period	20,000/min
Unrealized FX Gain Loss Report	Home currency is set; The invoice/debit memo/credit memo/unapplied payment which has none zero balance as of accounting period end date	14,000/min

For example,

The following table shows how to calculate the duration for each report type based on the total transactions data volume and throughput:

Type	Total Transactions Data Volume	Throughput	Duration
AR Aging Report	1,000,000	120,000/min	8.33 min
AR Detail Report	5,000,000	400,000/min	12.5 min
Revenue Detail Report	10,000,000	400,000/min	25 min
Realized FX Gain Loss Report	3,000,000	20,000/min	150 min
Unrealized FX Gain Loss Report	200,000	14,000/min	14.28 min

The trial balance job duration is determined by the longest subtask. In this example, the “Realized FX Gain Loss Report” is the longest with a duration of 150 minutes.

Notes

The trial balance formula are reference speeds when Performance Booster is enabled.
The average throughput is based on the assumption that the customer uses 3 to 4 segments on common objects and has currency conversion enabled. For customers using more complex segmentation, trial balance may take longer than stated in the example above.
The performance metrics are based on basic AWS hardware configuration. Better hardware can further improve performance.