1 |
On Tuesday 12 Aug 2014 07:42:46 Alan McKinnon wrote: |
2 |
> On 12/08/2014 07:36, J. Roeleveld wrote: |
3 |
> > On Monday, August 11, 2014 10:45:07 PM Mick wrote: |
4 |
> >> On Monday 11 Aug 2014 20:01:16 Volker Armin Hemmann wrote: |
5 |
> >>> isn't it great? back in the days when kmail stored emails in files, |
6 |
> >>> everything worked great and even folders with 100k mails were not a |
7 |
> >>> problem. |
8 |
> >>> |
9 |
> >>> But, no, they had to break that. |
10 |
> >>> |
11 |
> >>> I lost ca 500k emails thanks to akonadi-crap and errors like that. I |
12 |
> >>> really loved kmail and thunderbird is garbage compared - but akonadi |
13 |
> >>> took away that choice. |
14 |
> >>> |
15 |
> >>> Thank you, kdepim-devs for making the dumbest decision ever! *thumbsup* |
16 |
> >> |
17 |
> >> I share your feelings although I haven't lost messages in my current |
18 |
> >> attempt to road test kmail2. I am dreading the moment when kmail1 will |
19 |
> >> stop working due to bitrot and I'll have to make a choice. :-( |
20 |
> > |
21 |
> > With a modern machine and the latest versions, it's not too bad and |
22 |
> > responds quicker then kmail-1 did. With the old version, I often had |
23 |
> > kmail become unresponsive when synchronizing the email. |
24 |
> > |
25 |
> > I didn't loose any emails, but that is more likely related to the emails |
26 |
> > being stored on an imap server, rather then being lucky. |
27 |
> > |
28 |
> > I really don't see the point of forcing mysql as a backend. Sqlite would |
29 |
> > have been a better choice. |
30 |
> |
31 |
> Way back when in the dark days of KDE-4.4 or thereabouts, the KDE devs |
32 |
> did do extensive tests with mysql vs sqlite and found sqlite lacking in |
33 |
> horsepower. Remember that it must store the metadata for all your mails |
34 |
> and some of us have lots of mail. IIRC there was also serious contention |
35 |
> issues with multiple threads. |
36 |
> |
37 |
> sqlite is an amazing little product, but it does have it's limits. It |
38 |
> performs really well as an embedded datastore to replace flat file |
39 |
> storage with an SQL interface, and my gut-feel evaluation is that it |
40 |
> runs out of steam at similar orders of magnitude of data. |
41 |
> |
42 |
> Amarok incidentally has almost exactly the same issues and the same |
43 |
> solution was adopted |
44 |
|
45 |
Only to add that it's more than just mail. It is the meta/data of the whole |
46 |
caboodle of the PIM suite of applications. |
47 |
|
48 |
I recall the devs explicitly stating early enough in the KDE4 development that |
49 |
sqlite is not man enough for the job and advising everyone to move over to |
50 |
mysql. |
51 |
|
52 |
Someone was looking at postgresql as an alternative to mysql, but I'm not sure |
53 |
that this would bring any benefit. |
54 |
|
55 |
-- |
56 |
Regards, |
57 |
Mick |