Re: Not all that much better with PostgreSQL

Hi Daniel.

Thank you for your answer.

Daniel Vrátil - 17.04.19, 15:46:
> On Friday, 12 April 2019 21:57:21 CEST Martin Steigerwald wrote:
> > Erik Quaeghebeur - 12.04.19, 21:00:
> > > On vrijdag 12 april 2019 20:55:41 CEST, René J.V. Bertin wrote:
> > > > I agree that akonadi has a long-standing dire need for job
> > > > manager interface […] a big button to stop all
> > > > processing, and buttons for each individual job to stop or pause
> > > > it. […]
> 
> Then plan is to rather be able to run multiple tasks in parallel so
> the indexing agent requesting the maildir resource to load every
> single email you have from the storage would no longer block requests
> from KMail to retrieve a single email to display to the user.

That sounds awesome.

I hope this brings a major relief.

For now I keep Akonadi with PostgreSQL. Its better than with MariaDB so 
far. Quite a bit better and with above issue fixed… let's see.

> > > Akonadiconsole has something a bit like that: Right-click an
> > > agent/resource and select ‘Abort activity’. It has actually come
> > > in
> > > handy once or twice for me, even though it is not fine-grained.
> > 
> > Thanks for the hint.
> > 
> > KMail often also has this when you expand progress indicator bar.
> > Just I found it often to have no effect whatsoever.
> > 
> > Well… after that longer lasting indexing completed, it is still
> > considerably better with PostgreSQL. So I am happy I changed.
> > 
> > I have the impression it can do more in parallel. I was able to
> > delete a mail while filtering was ongoing. That did not work
> > before. I read in a article about improvements in just released
> > major PostgreSQL version that PostgreSQL can do some queries in
> > parallel that MariaDB/MySQL would so sequentially. So this may
> > help.
> 
> David Faure did a *lot* of work to track down and fix the database
> deadlock issues we had with MySQL (and with PostgreSQL as well, they
> just did not show up that much), you should see a lot of improvement
> in speed and reliability in the upcoming releases.

David just blogged about it:

https://blogs.kde.org/2019/04/17/2019-toulouse-pim-sprint-report

Thanks,
-- 
Martin