Bug 226115 - Use Virtuoso for Akonadi storage
Summary: Use Virtuoso for Akonadi storage
Status: RESOLVED INTENTIONAL
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.3
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 08:47 UTC by underscore
Modified: 2013-03-03 14:21 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description underscore 2010-02-10 08:47:05 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

Akonadi uses MySQL and 
Nepomuk uses Virtuoso.

As Virtuoso is also a SQL Database it should be possible to merge both data repositories into one engine, saving a lot of memory and system ressources in turn.

Even a driver for akonadi is readily available in QT with the unixodbc driver.
Comment 1 Ritesh Raj Sarraf 2010-02-10 08:52:58 UTC
Same should go for Amarok too.
Comment 2 Till Adam 2010-02-10 12:20:56 UTC
We're actively looking into this fyi, there are some blockers, atm, like glitches in the virtuoso odbc implementation feature reporting, etc. Being worked on, in any case.
Comment 3 Alejandro Nova 2010-07-05 17:01:41 UTC
I tried for the first time KDEPIM 4.5. The performance is awful unless I configure Akonadi, using some SQL commands and parameters, to use a system wide and specially tuned MySQL server running in my laptop. MySQL may spike to 30% for short bursts using my settings (200 MB for cache, I don't remember the specifics but I can upload my my.cnf if you want to), but, with a stock Akonadi riding its own database, the CPU usage stays solid at 80% for several minutes or even hours (when updating a 2GB IMAP disconnected account with KMail 1.80).

This, guys, is a must. I don't care about the benchmarks, because if I manage to allocate 100 MB of RAM more to Virtuoso using the RAM previously devoted to a MySQL server I can get a better performance anyway (the same thing I did previously to unify Amarok, Digikam and Akonadi around the same system-wide MySQL server)
Comment 4 Rico Rommel 2011-07-27 20:07:27 UTC
Is there anything new about it?
Comment 5 Christophe Marin 2012-01-02 14:00:41 UTC
(In reply to comment #4)
> Is there anything new about it?

no
Comment 6 Daniel Vrátil 2013-03-03 14:21:36 UTC
Virtuoso architecture is not really suitable for this use-case and since Nepomuk developers are considering to abandon Virtuoso in favour of sharing DB with Akonadi, this wish most probably not going to be ever implemented.