Issue Feature Under Review Stale

#110189Add SQLite performance mode option to the installer

Michael Staatz 07/12/26, 10:58 updated 07/17/26, 04:44

Description

Currently, when choosing SQLite as the database driver during installation, TYPO3 creates the database file using SQLite’s out-of-the-box defaults.

These defaults are conservative and not well suited for web application workloads — most notably, the default DELETE journal mode causes significantly more disk I/O than the WAL (Write-Ahead Logging) mode, and several other PRAGMA settings (synchronous, busy_timeout, cache_size, foreign_keys, temp_store) are left at their compile-time defaults rather than values commonly recommended for this use case.

This patch adds a new option to the database driver selection step of the installer: “SQLite (performance mode, WAL)”, alongside the existing “Manually configured SQLite connection” option.
When selected, the following PRAGMAs are applied via the connection’s initCommands at the time the database file is created:

PRAGMA auto_vacuum = INCREMENTAL PRAGMA journal_mode = WAL PRAGMA synchronous = NORMAL PRAGMA busy_timeout = 5000 PRAGMA cache_size = -20000 PRAGMA foreign_keys = ON PRAGMA temp_store = MEMORY

Note that the order of these PRAGMAs matters: auto_vacuum only takes effect on a still completely empty (0-byte) database file.
Any other PRAGMA or write operation, including switching to journal_mode = WAL, initializes the file header and silently turns any subsequent auto_vacuum change into a no-op. auto_vacuum is therefore applied first.

These recommendations are based on the widely referenced SQLite tuning guide at https://briandouglas.ie/sqlite-defaults/, which is also linked from TYPO3’s own blog post on using TYPO3 with SQLite for small projects (https://typo3.com/blog/using-typo3-for-small-projects).
This is a pure opt-in addition — the existing “Manually configured SQLite connection” option remains completely unchanged, so there is no behavior change for existing installations or workflows.

Reviews 1

History 14

  1. Michael Staatz commented <span data-processor="relativetime" data-value="2026-07-13T03:15:19+00:00" > 07/13/26, 03:15 </span>

    Related DDEV fix (required for this feature to work with DDEV’s
    default TYPO3 project setup): https://github.com/ddev/ddev/pull/8582