Optimisations

This page has information on the various optimisation levers & tradeoffs that Flux offers.

Disabling Audit Logs

Audit logs are captured in Flux to show all state transitions. The number of audit records generated is generally about 3-4X times the number of state changes, if not more. This has an I/O and storage cost as the data in stored in the Flux database. While frequent purging/archival of the Audit records (can be done outside the Flux runtime by directly using the database tools), users may also completely turn off audit capture. Note that by turn off audits, the Flux view of workflow executions will not display the trail of transitions.

Auditing may be turned off by setting the enableAuditRecord to 'False' in the Flux config files, depending on the runtime modes - i.e configuration.yml or executionConfiguration.yml or orchestrationConfiguration.yml