Hi!

I run ARCH linux with KDE 4.11. Because I have a Mysql server running on my system anyway I decided to go with the option for Akonadi to NOT use the internal server.

So I connected to an akonadi database on my localhost mysql daemon. But now the Mysql server runs with the normal default settings as layed out in /etc/my.conf ...

Where is the user file located to adjust the mysql settings for the akonadi database?

When searching this I always get the hint to look into ~/.local/share/akonadi/mysql-global.conf ... but this file doesn't exist and I think it only applies to the internal mysql server for akonadi ...

akonadiserverrc doesn't specify any .conf file either ...

Plz: How do I get the correct settings for the akonadi mysql client to be used by mysql (without messing up all the other mysql clients for other programs)?

thx for reading,
p.

p.s.: Or do I have to set some options in the akonadi Configuration dialog in KDE?

Noone?

Since the documentation on the akonadi/mysql connection is very limited (well there is so much stuff to read but most is outdated or not the recommended way to do things or just not working...) anything would help here:

1. If I do not use the akonadi internal mysql which file for MYSQL configuration is applied?
2. Do I need any settings in the line "options" in the akonadi server configuration dialog?

plz help someone,
thx piedro

piedro wrote:1. If I do not use the akonadi internal mysql which file for MYSQL configuration is applied?

If you're using an external mysql server, it uses its own settings of course (i.e. /etc/my.conf and /etc/mysql/).
It could even run on a different host in the network.

2. Do I need any settings in the line "options" in the akonadi server configuration dialog?

No.
Although I would recommend adding "MYSQL_OPT_RECONNECT=1", so akonadi will automatically reconnect if a timeout occurs.
Otherwise you may have to restart akonadi after some idle time (mysql's default timeout setting is 8 hours AFAIK).

Edit:
And if your mysql server is configured to keep a binlog, you may want to exclude the akonadi database from that (option "binlog-ignore-db = akonadi" in /etc/my.conf).
Otherwise the binlogs could grow a few GBs per day...

thx wolfi!

So it seems that maybe instead of using the external server it is a bit more practical to run the internal mysql solution.
By doing this I would be able to benefit from all the akonadi specific optimizations of the KDE team in their "mysql-global.conf" file.
I looked into it and there are many settings of which I have no clue whether (if put into my.onf) they would have a negative impact on the other databases on the mysql server. It might be preferrable to run it with something close to defaults ...

But first I will try your reconnect setting (takes a while I guess) and see how it goes ...

Offtopic: I wonder why this forum is si much quicker and more competent than the official KDE forums ... I will stay here from now!

So thx again,
I'll keep posting any results,
piedro

piedro wrote:So it seems that maybe instead of using the external server it is a bit more practical to run the internal mysql solution.
By doing this I would be able to benefit from all the akonadi specific optimizations of the KDE team in their "mysql-global.conf" file.
I looked into it and there are many settings of which I have no clue whether (if put into my.onf) they would have a negative impact on the other databases on the mysql server. It might be preferrable to run it with something close to defaults ...

Well, I'm running akonadi with an external mysql server for years now (with the default mysql settings), and it works very well here.
I had to exclude the akonadi database from the binlog as mentioned, because my hard disk filled up.
But that was because binlog was enabled on openSUSE by default (this has been changed by a recent update though...)
It may be different on your distribution.

Offtopic: I wonder why this forum is si much quicker and more competent than the official KDE forums ... I will stay here from now!

Hm, I don't understand?
AFAIK this _is_ the official KDE forum (forum.kde.org).

Hello Again!

So I am very confident then. I used your settings for external now and hope for the best!
I am on Arch and the binlog is turned off by default.

So thx a lot (also for clarifying the forum status),
cya, piedro

piedro wrote:So I am very confident then. I used your settings for external now and hope for the best!
I am on Arch and the binlog is turned off by default.

So thx a lot (also for clarifying the forum status),

You're welcome.

But don't forget to report back here.
I don't take any responsibilities, YMMV...
But as I said, it works fine on my system.

Btw, what forum did you report this to before?
Because you said, this one is "much quicker and more competent than the official KDE forums".
I'm just wondering...

And, if you feel so, please mark this thread as solved (there should be a button "Accept this answer" at the bottom of every post)...

Hi wolfi323!

Sorry it took a while to test long uptime. Your hint seems really good. Actually it seems this fixes a lot of performance problems I had with KDE before. Things are running very smooth at the moment (might be a coincidene) but I think this should simply be th default setting.

Though I still have lots of issues with Kmail and Kontact (like: I have to turn off email filtering, I still have "ghost" emails deleted and greyed out but they don't vanish ... and much more ,,,) but overall even issues like kjots refreshing notes all the time, doubling folders and loosing notes, seems to be fixed when using "MYSQL_OPT_RECONNECT=1".

On a critical note though: If the whole akonadi functionality is so severerly dependent on an continuing mysql connection to run smoothly without producing severe breakage then I think there are some fundamental concept flaws. Not every environment will be consistent with this requirement and there should be solid emergency measures on the akonadi part to prevent everything from falling apart once the mysql connection is disturbed ...

So thx again, I marked it as solved,
piedro

p.s.: sorry the whole forum thing was a mistake on my part, I am sure the other community (which is a local one) does as best as can with good intent. I shouldn't have started bashing anyone in the first place. My bad. And I won't continue on that route ... (though I completely switch to this forum here now ... )

piedro wrote:Things are running very smooth at the moment (might be a coincidene) but I think this should simply be th default setting.

What do you mean? The "MYSQL_OPT_RECONNECT=1" option or the external mysql server?
If it's the latter, well that's a bit problematic. You can't really expect every user to install and set up a mysql server. Akonadi should work out-of-the box on a fresh KDE installation.

Though I still have lots of issues with Kmail and Kontact (like: I have to turn off email filtering, I still have "ghost" emails deleted and greyed out but they don't vanish ... and much more ,,,)

Hm. I never had that.
I still have the problem that some mails get duplicated during filtering, but that doesn't really bother me anymore since I mostly use IMAP and server-side filtering now...

You could try to disable the nepomuk email indexer as a test (or set all your mail folders not to be indexed, that's what I have done a while ago. For my needs the normal filter bar is working good enough anyway). Maybe those problems disappear then?

On a critical note though: If the whole akonadi functionality is so severerly dependent on an continuing mysql connection to run smoothly without producing severe breakage then I think there are some fundamental concept flaws. Not every environment will be consistent with this requirement and there should be solid emergency measures on the akonadi part to prevent everything from falling apart once the mysql connection is disturbed ...

Well I guess that's another reason why an internal mysql server is the default.
But actually as far as I know this should be fixed in the next akonadi version (1.10.3).
But still having that option set won't hurt either of course...

Hi again!

Yes. I thought that only if you use the external server option this should be a default option.

There are some more good points you suggest. I will try some options as soon as I get the time to do so ... maybe a while, but I will report back if there is some success ...

On the point with the internal server as default, hmm, it's against all my technical intuitions to have a mariadb server on my localhost anyway and let akonadi run it's own in addition. But maybe this is actually the best way to go ... one has to challenge intuitions from time to time to progresss ...

But as said:
It's running much better than before atm and I am curious to see the changes with the new version you mentioned.

thx a lot,
p.