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.mckin...@gmail.com
