When you set up the audit configuration through the audit policies, be sure that you are auditing only those events you want to record. The more audit events you set up, the higher the amount of overhead time auditing consumes, taking away from application data operations.
You can ask your database administrator to use the PROUTIL utility to disable building of all the optional indexes on the audit data tables. You would normally do this if you are not going to run audit reports against them.
This practice is recommended when you regularly archive audit data to a database dedicated to holding long-term audit data. Enable full index support only on the dedicated, long-term audit database.
You can also configure auditing to store old and new field values, no values, new values only, or old values only. The less you store, the more efficient the auditing performance is.
