KPI statistics for Levenshtein distance and post-editing time will be enabled now by default and may require significant processing time on large databases. They can run automatically during an update or be triggered manually alongside the active installation. To skip automatic statistics generation during update, set: resources.db.statistics.enabled = 0 in installation.ini before starting the update. To generate statistics manually after the update, set the flag to 1 and run: statistics:sqlite:init --aggregate. Note for installations with statistics already enabled (resources.db.statistics.enabled = 1): Starting with this release, the default statistics engine has been changed to sqlite. If you want to continue using the previous default (mariadb), add the following to your installation.ini: resources.db.statistics.engine = "mariadb"