Martin Schlander wrote:

Lørdag den 6. august 2011 04:40:34 skrev Constant Brouerius van Nidek:

...

On Friday, August 05, 2011 11:27:09 PM Malte Gell wrote:

...

Hi there,

I use kmail-4.7.0-10.1.x86_64 and whenever I open an email folder, be it an IMAP folder or local folder with email fetched from POP3 accounts, it sometakes takes very long (up to one minute) until the folder is accessable.

Is there something I can do to fasten opening email folders? It is annyoying when you have many folders and each takes ages to open....

+1, and if it cannot made faster, it would be nice to have some sort of indication about the progress of the process.

Maybe that's the benefits of using sqlite instead of mysql? ;-) New KMail was supposed to be faster, especially for imap.

/Martin who plans to make his initial tests of migration to akonadified pim tomorrow

I did this move yesterday. I am still using the MySQL backend and did not make the change to SQLite. Among the first things that happened was Nepomuk crashed twice. When it ran and I started Kontact for the first time the migration tool ran. I just went along with it. It seemed to do OK for Akkregator, Notebooks, Contacts, and Knode, but was incomplete for Kmail. It had set all my smtp accounts to the default mail server and all identities likewise. I stopped Kmail. Briefly looked at Akonadiconsole and cleaned up a couple of straggling dupes and empty resource. Deleted kmailrc and started Kontact again. I manually repaired all migration failures in smtp outbound accounts and identities (each user ID account points to a different smtp outbound server account and this was broken in the migration). After ensuring all smtp and identities were config'd correctly I recreated all my receiving accounts. All has been fine ever since. The one thing I do notice is when freshly booting the box and starting the desktop Nepomuk chews some serious CPU cycles (temp goes up, fan runs faster) for a couple of minutes. But when it's done it's good; I have not had a crash like the two from the very beginning of the process. Overall, after cleaning up a semi-botched migration it has run very well since. -Mike -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Sat, 06 Aug 2011 13:04:04 +0530, phanisvara das wrote:

On Sat, 06 Aug 2011 12:07:38 +0530, Martin Schlander wrote:

...

Maybe that's the benefits of using sqlite instead of mysql? New KMail was supposed to be faster, especially for imap.

it's using sqlite only for new setups, i think. i have been using akonadi with mysql for a long time, and after upgrading to 4.7 it's still using mysql, not sqlite. it was explained, somewhere on this list i think, that the existing setup wouldn't be changed, but new ones default to sqlite.

and i don't experience this slow switch to another folder, i forgot to mention. kmail2 takes a little time to read all the folders when i start if first after logging in, but then switching folders is pretty instantaneous. those who experience that slow-down all the time might want to check if their akonadi setup uses mysql or sqlite, and if the latter, try to change it to mysql. -- phani. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org

On Mon, 08 Aug 2011 19:48:22 +0530, Malte Gell wrote:

You mean, change to sqlite? Sqlite was meant to be faster not MySQL? How do i change Akonadi to sqlite?

no, i meant it the other way around: change to mysql if you're using sqlite at present and are not happy with it. the last time i played around with my akonadi configuration was a long time ago though, and things have changed a lot since then. at present you find the relevant config. in ~/.config/akonadi/akonadiserverrc i believe, but before actually making changes there i'd ask someone who knows better than i. (what i'd do is create a new user, mess around with that, and delete when done.) if i remember correctly, mysql was changed for sqlite as the default because in many cases mysqld didn't work at all; so it's certainly not a solution that'll work for everyone, in every situation. somehow i'm fortunate that i had mysqld configured & in working order, and KDE 4.7 stuck to that. -- phani. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org