Performance Metrics of Journal Run
This article contains details of the performance metrics of a journal run. For more information, see Journal Run.
Performance metrics calculation
Performance metrics is calculated using the following method:
A Zuora Journal Run Duration(in minutes) ≈ Max of (Number of transactions being processed / Average Transaction Processing Throughput)
Average Transaction Processing Throughput = 40,000 / min
Note that each transaction type is processed in parallel, so the total execution time of journal run depends on the transaction type with the maximum transactions.
For example,
- A Journal Run processes 1,000,000 Invoice Items (The maximum number of transactions in the journal run are of type ‘Invoice Item’)
- Average Invoice Item Processing Throughput = 40,000 / min
so,
Journal Run Duration ≈ 1,000,000 / 40,000 = 25 mins
Notes
- The journal run benchmarks in this article are reference speeds when Performance Booster is enabled.
- The average throughput is based on the assumption that the customer uses 3~4 segments on common objects (such as Account, Product, Product Rate Plan) and has currency conversion enabled. For customers using more complex segmentation, Journal run 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.
- The performance booster may not be effective if you execute the journal run immediately after the monthly bill run and payment run. Allow intervals for the performance booster to become effective, and then execute the journal run.