To improve the performance of sessions in which new order numbers are assigned, you can define a cache size for a series. The cache size is the number of new series numbers that ERP LN generates at once. If there are series numbers in cache, users do not have to wait while ERP LN generates and checks the next series numbers.
Cache size = 0
No caching is applied. If you request a new number, the number is only committed after the transaction to which the number applies is completed.
Disadvantage: The number series is locked during the transaction. Other users cannot request a new number from the same series until the transaction is completed.
Advantage: No numbering gaps.
Use a cache size of 0 if number gaps are not allowed. Preferably, request a new number close to the end of a transation to reduce locking time. In high volume implementations, a cache size of 0 may cause performance and locking issues.
Cache size = 1
If you request a new number, the number is committed immediately, even if the transaction to which the number applies is not yet completed.
Disadvantage: Numbering gaps may occur if a transaction is not finished.
Advantage: The number series is locked for only a short time, which improves performance.
A cache size of 1 is the default value for number series. In this way, performance and locking issues in high volume implementations are avoided as much as possible.
Cache size > 1
The value of the cache size indicates how many new numbers are requested at once. The numbers are committed immediately, even if transactions are not yet completed.
Disadvantage: Large numbering gaps may occur if more than one transaction is unfinished.
Advantage: The number series is locked for only a short time. Furthermore, for all numbers that are requested, the number series needs to be updated only once, which improves performance.
A cache size larger than 1 is only recommended if a cache size of 1 does not solve locking issues sufficiently.