Bug 417071 - Akonadi is constantly writing to disk.
Summary: Akonadi is constantly writing to disk.
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.12.3
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-02 19:15 UTC by Hakan Bayindir
Modified: 2020-05-10 13:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
One day of iotop statistics, running in cumulative mode, sorted by disk write. (1.76 MB, image/png)
2020-02-02 19:15 UTC, Hakan Bayindir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hakan Bayindir 2020-02-02 19:15:48 UTC
Created attachment 125624 [details]
One day of iotop statistics, running in cumulative mode, sorted by disk write.

SUMMARY
Akonadi is constantly writing to disk and creating a lot of cumulative disk I/O after some time.

STEPS TO REPRODUCE
1. Run akonadi.
2. Leave it turned on for the day.
3. Enable indexer for better results.

OBSERVED RESULT
~3.5GB written to the disk after 10 hours of operation.

EXPECTED RESULT
A milder disk write pattern.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Testing.
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5

ADDITIONAL INFORMATION
KMail is also managing a single IMAP account via Akonadi. Continually writing small amounts of data wears SSDs pretty fast.
Comment 1 Hakan Bayindir 2020-05-10 13:17:49 UTC
I have found the root cause of constant writing to disk, however it needed a good amount of digging with akonadiconsole.

A malformed e-mail was triggering akonadi indexer to constantly retry indexing a bunch of entries every two seconds or so. This caused constant writing to the disk.

Finding the offending collection ID and removing all mails (it was luckily trash) fixed the problem.

I'm leaving the state as REPORTED intentionally because I still think the behavior is suboptimal and I'm not knowledgeable enough to decide its future.

If the maintainers can do the right thing, I'd be grateful.