| Prev | Next |
Auditing Performance
Enabling auditing on a project increases the time taken for many actions, such as insertion, change and deletion of objects and changes to properties of elements, connectors and diagrams, including moving objects in diagrams. When auditing is initially enabled, the time required to write to the audit logs will be almost imperceptible, but as the logs grow in size the log write time will become longer and could cause some frustration to you or your colleagues, whose main focus is creating useful models. Fortunately there are some simple housekeeping and administration procedures that can reduce this time, typically performed by a Librarian or Administrator.
Operation Delays
Operation |
Detail |
See also |
|---|---|---|
|
Large Deletions |
Deleting large Packages or Package structures, or large numbers of elements, takes significantly longer with auditing on. You might disable auditing before performing such a deletion. |
Auditing Settings |
|
XMI Imports |
Importing XMI takes longer with auditing enabled. A project-level option is provided for disabling auditing of XMI Imports. |
Import from XMI Audit Settings |
|
Reverse Engineering |
Reverse engineering code takes longer with auditing enabled. A project-level option is provided for disabling auditing of reverse engineering. |
Importing Source Code Audit Settings |
|
Replication |
You cannot remove replication from a model with Auditing enabled. If you have to remove replication, disable Auditing and - if prompted to do so - allow Enterprise Architect to roll back the database version; you can then remove replication. |
Remove Replication Auditing Settings |