File: gdbm.info,  Node: Performance Impact,  Next: Availability,  Prev: Manual crash recovery,  Up: Crash Tolerance

17.6 Performance Impact
=======================

The purpose of a parachute is not to hasten descent.  Crash tolerance is
a safety mechanism, not a performance accelerator.  Reflink copying is
designed to be as efficient as possible, but making snapshots of the GNU
dbm database file on every 'gdbm_sync' call entails overheads.  The
performance impact of 'GDBM' crash tolerance will depend on many factors
including the type and configuration of the underlying storage system,
how often the application calls 'gdbm_sync', and the extent of changes
to the database file between consecutive calls to 'gdbm_sync'.