Nepomuk

[O. Sinclair]

On 21/12/11 14:05, Alvin wrote:
> On Saturday 17 December 2011 20:46:38 Steve Riley wrote:
>> I suspect some of bloat, and a contributor to the claims that KDE "feels
>> slow," has to do with the sheer number of databases. I'm experimenting with
>> building a KDE system by hand. So far, three separate databases are
>> installed:
>>
>> * MySQL for Akonadi
>> * Sqlite for Quassel
>> * Virtuoso for Nepomuk
>>
>> Quassel is hardcoded to depend on Sqlite. Akonadi can be switched to that as
>> well, but some docs on KDE.org warn against that, claiming performance will
>> suffer. Nepomuk is similarly wedded to Virtuoso through Soprano. Surely
>> there has to be a better way.
>
> You forgot *Digikam* and *Amarok*.
> I'm running quassel in the client-server setup with postgres as backend, left
> Amarok alone and use postgres for Akonadi.
>
> Unfortunately, that doesn't help much. Virtuoso is the real offender here. I
> don't understand what it indexes. Search in Kmail doesn't work anyway. It
> never returns any results.
>
> I'm in the same boat as O. Sinclair. I /like/ Kontact (and even the Akonadi
> idea). The features are perfect, but the bugs are too numerous and performance
> is very, very bad.
>
> Here's to hope!
>
Happy to hear I am not the only one, watching Nepomuk again reindexing 
my mp3 files - must be 3rd or 4th time in 48 hours. And as I understand 
strigi is the "underlying" indexer here - but the chain is so complex it 
is more than easy to lose track.