https://bugs.kde.org/show_bug.cgi?id=456024
Bug ID: 456024
Summary: Use Write-Ahead-Logging as default journalling mode
Product: digikam
Version: 7.6.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: zil...@gmx.com
Target Milestone: ---
SUMMARY
***
Each Digikam db still uses "delete" journalling mode, while WAL was introduced
in 2010 and is over and over again confirmed to be more efficient. Especially
on Linux with EXT4 or BTRFS filesystem users will benefit from changing journal
mode to WAL instead of delete.
***
STEPS TO REPRODUCE
1. Please find benchmark results here.
https://wiki.tnonline.net/w/Blog/SQLite_Performance_on_Btrfs
2. Note although these are specific for BTRFS filesystem as it will benefit
even more because it is a CoW filesystem, EXT4 will benefit too. This is not a
btrfs-specific request, although constant DB changes do require btrfs users to
change journal mode to WAL.
OBSERVED RESULT
See results here: https://wiki.tnonline.net/w/Blog/SQLite_Performance_on_Btrfs
EXPECTED RESULT
- improved performance on EXT4
- required for BTRFS
SOFTWARE/OS VERSIONS
All Linux systems using EXT4 or BTRFS filesystem.
ADDITIONAL INFORMATION
Note every other software I come across already uses journal_mode=WAL instead
of journal_mode=delete.
I requested this over a year ago through the mailing list as well as it seems
like a trivial thing to do.
Users can do it manually, but should not be required to do so.
--
You are receiving this mail because:
You are watching all bug changes.
