Password hashing configuration.
Rules for persisting key-value changes. Default persistence is to immediately persist all changes. While this ensures data integrity, the overhead of the key-value store can be significantly reduced by utilizing lazy persistence strategies that delay writing changes until certain thresholds have been met.
A threshold controlling lazy commits. For a threshold to apply, both
number_of_changes must be met or surpassed and
duration must have
elpased since the last commit.
Configuration options for background tasks.
Automatic configuration based on execution time. This is measured during the
Configuration options for views.
Storage configuration builder methods.