Which setting has the most negative impact on map performance?

Map Retry only incurs overhead when a map actually fails and a retry is attempted, so it has no impact on successful map executions and minimal overall performance cost.

Audit Log records only summary-level information at map start and end, producing far fewer log writes than Map Trace and therefore causing a much smaller performance impact.

Map Trace generates granular log entries for each individual rule execution and data element transformation throughout the entire map run, creating significant I/O overhead and memory consumption. This level of detail far exceeds that of Audit Log, which only records high-level map start and completion events. Because Map Trace operates on every processing step rather than at the map level, its performance penalty scales with map complexity and data volume.

Backup copies input and output data for recovery purposes but involves a single file operation per map execution, which is far less overhead than the continuous per-rule logging performed by Map Trace.