TAIL

By using WCC, you can account for additions and modifications that are made to parties with
the Transaction Audit Information Logging (TAIL) service. In order for the service to provide
this information on demand, any WCC services that add or modify data will have an additional
overhead when TAIL is enabled.
Consider the following points regarding performance when you enable TAIL:
Complex WCC transactions typically contain other services. TAIL keeps an internal log of
these child services for auditing purposes. Therefore, the more business objects you
modify or change, the more overhead you are likely to experience.
The WCC services that retrieve data from the TAIL tables are often low in a transactional
workload and are not typically a performance concern. The only concern is the WCC
services and those transactions that modify or add data because they will trigger TAIL.
TAIL overhead can add up to 45% to response times of add and update transactions,
depending on the amount of WCC business objects being modified.
TAIL overhead is the same for both add and update transactions.
TAIL decreases TPS in those affected transactions in proportion to the overhead it adds.
TAIL does not introduce any bottlenecks that might impact other transactions in the
workload.
TAIL increases usage on the WCC database tables of TRANSACTIONLOG,
INTERNALLOG, INTERNALLOGTXNKEY, and INTERNALTXNKEY.