Re: KDEPIM with SQLite3

Greetings Soren, greetings.

Soren Stoutner - 28.02.26, 21:06:53 CET:
> On Saturday, February 28, 2026 2:20:29=E2=80=AFAM Mountain Standard Time =
Martin
> Steigerwald wrote:
> > Akonadi SQLite3 continues to be faster and more robust than with
> > MariaDB or PostgreSQL for me. But unfortunately it is still not
> > perfect. At least with POP3 mail retrieval there can still be quite
> > odd delays. With a light IMAP account I have in another setup it
> > works nicely.
>=20
> My personal experience is that with a large IMAP system (125 MiB
> akonadi.db file) it freezes a lot with SQLite3, particularly when
> deleting large amounts of emails.  Sometimes those freezes can last
> minutes, during which, if further deletion of emails is attempted, they
> GUI continues to display them.  In some instances, the deletions are
> queued and later processed.  In other instances the deletions are never
> processed.  I assume it is because the database is being compacted and
> it takes a while to process.

You did not have that with MariaDB or PostgreSQL? Do you see any Akonadi=20
process activity? I think SQLite3 should be running within Akonadi's main=20
process: /usr/bin/akonadiserver.

I did have those pauses during POP3 retrieval also with MariaDB and=20
PostgreSQL. In fact I have them since a very long time. And I think the=20
issue is even known upstream:

Look at how to improve pop3 support

https://invent.kde.org/pim/pim-technical-roadmap/-/issues/36

Also I do not see any relevant KDEPIM / Akonadi process activity. It is=20
just sitting there, idle. Or waiting on=E2=80=A6 whatever.

Best,
=2D-=20
Martin