# Replay Configuration

You can tune the `snapshot-trigger-size` and `snapshots-to-keep`[Engine Variables](https://docs.singlestore.com/db/v9.1/reference/configuration-reference/engine-variables.md) to make efficient use of the logs and snapshots.

A large `snapshot-trigger-size` decreases the frequency that snapshots are taken. But a large `snapshot-trigger-size` increases the time needed to replay the snapshot.

A large `snapshots-to-keep` increases the number of snapshots available, and it increases the amount of space needed to store the snapshots and logs.

`snapshots-to-keep` defaults to `2`.

The `datadir` engine variable stores the location of the snapshots and logs.

See [Managing Disk Space Used by Transaction Logs](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/high-availability-and-disaster-recovery/transaction-logs-snapshots/manage-disk-space.md) and [Configuring Transaction Logs and Snapshots](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/high-availability-and-disaster-recovery/transaction-logs-snapshots/configure.md) for more information.

***

Modified at: February 10, 2022

Source: [/db/v9.1/user-and-cluster-administration/high-availability-and-disaster-recovery/transaction-logs-snapshots/replay-configuration/](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/high-availability-and-disaster-recovery/transaction-logs-snapshots/replay-configuration/)

(An index of the documentation is available at /llms.txt)