From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] akonadi ... don't you just love it?
Date: Tue, 12 Aug 2014 08:42:46 +0200 [thread overview]
Message-ID: <53E9B766.7040607@gmail.com> (raw)
In-Reply-To: <1573911.bTZgDrGOdb@andromeda>
On 12/08/2014 07:36, J. Roeleveld wrote:
> On Monday, August 11, 2014 10:45:07 PM Mick wrote:
>> On Monday 11 Aug 2014 20:01:16 Volker Armin Hemmann wrote:
>>> isn't it great? back in the days when kmail stored emails in files,
>>> everything worked great and even folders with 100k mails were not a
>>> problem.
>>>
>>> But, no, they had to break that.
>>>
>>> I lost ca 500k emails thanks to akonadi-crap and errors like that. I
>>> really loved kmail and thunderbird is garbage compared - but akonadi
>>> took away that choice.
>>>
>>> Thank you, kdepim-devs for making the dumbest decision ever! *thumbsup*
>>
>> I share your feelings although I haven't lost messages in my current attempt
>> to road test kmail2. I am dreading the moment when kmail1 will stop
>> working due to bitrot and I'll have to make a choice. :-(
>
> With a modern machine and the latest versions, it's not too bad and responds
> quicker then kmail-1 did. With the old version, I often had kmail become
> unresponsive when synchronizing the email.
>
> I didn't loose any emails, but that is more likely related to the emails being
> stored on an imap server, rather then being lucky.
>
> I really don't see the point of forcing mysql as a backend. Sqlite would have
> been a better choice.
Way back when in the dark days of KDE-4.4 or thereabouts, the KDE devs
did do extensive tests with mysql vs sqlite and found sqlite lacking in
horsepower. Remember that it must store the metadata for all your mails
and some of us have lots of mail. IIRC there was also serious contention
issues with multiple threads.
sqlite is an amazing little product, but it does have it's limits. It
performs really well as an embedded datastore to replace flat file
storage with an SQL interface, and my gut-feel evaluation is that it
runs out of steam at similar orders of magnitude of data.
Amarok incidentally has almost exactly the same issues and the same
solution was adopted
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-08-12 6:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 20:00 [gentoo-user] akonadi ... don't you just love it? Mick
2014-08-10 9:34 ` J. Roeleveld
2014-08-12 7:05 ` Mick
2014-08-11 18:01 ` Volker Armin Hemmann
2014-08-11 21:45 ` Mick
2014-08-12 5:36 ` J. Roeleveld
2014-08-12 6:42 ` Alan McKinnon [this message]
2014-08-12 9:10 ` Mick
2014-08-12 12:06 ` Alan McKinnon
2014-08-12 13:28 ` J. Roeleveld
2014-08-12 13:38 ` Alan McKinnon
2014-08-12 14:10 ` J. Roeleveld
2014-08-12 18:21 ` Volker Armin Hemmann
2014-08-12 19:00 ` J. Roeleveld
2014-08-12 19:20 ` Alan McKinnon
2014-08-13 6:38 ` J. Roeleveld
2014-08-13 7:10 ` Alan McKinnon
2014-08-13 12:18 ` Alec Ten Harmsel
2014-08-13 12:26 ` Alan McKinnon
2014-08-11 19:05 ` [gentoo-user] " Mick
2014-08-11 22:21 ` Neil Bothwick
2014-08-12 0:38 ` Rich Freeman
2014-08-12 7:31 ` Neil Bothwick
2014-08-12 8:08 ` Peter Humphrey
2014-08-12 14:38 ` Daniel Frey
2014-08-12 17:54 ` Rich Freeman
2014-08-12 1:00 ` Dale
2014-08-12 7:57 ` Walter Dnes
2014-08-12 8:19 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E9B766.7040607@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox