|Administration Guide / Repository Server Management|
Each TestArchitect repository maintains a log, known as the hit list, of database transactions (items checked in, items checked out, etc.) over time. Normally, the repository server writes to this log in real time for every transaction, in an operation referred to as "hit list clearance". As the log grows, this constant maintenance can cause performance to take a hit. The alternative is to instruct the repository server to hold off on writing to the log, and instead cache the transaction records as each such operation occurs. Then, on a periodically scheduled basis, the log is updated with all the transactions in the cache, with the cache then cleared.
Scheduled hit list clearance is configurable for each given repository server. (It cannot be done at the repository level.) When in effect, period clearance can take place at a maximum frequency of daily, and minimum of weekly.
To create a hit list clearance schedule, perform the steps below:
[SETTINGS] duplicate hit reduction hour=23 duplicate hit reduction weekdays=1, 2, 3, 4, 5, 6, 7
[SETTINGS] duplicate hit reduction hour=23 duplicate hit reduction weekdays=3, 5, 7
[SETTINGS] duplicate hit reduction hour=2 duplicate hit reduction weekdays=1