> Nepomuk in 4.10 being too slow. Whichever bottlenecks they may be, are > "most probably" in our code. Not theirs.
There are bottlenecks in nepomuk, but there are in V as well. Once upon a time, I did some benchmarks with sql (sqlite) and sparql (virtuoso/soprano) queries for the things that are needed in kamd - the main being 'get all events from that to that timestamp, that belong to this application in that activity'. While the query in SQL is a simple filtering on a single table, in sparql it is a couple of joins. > problem with virtuoso. Though I have been dreaming about "maybe" > implementing something like this [1] on top of QtSql. While it has its > benefits, I'm not sure it would be a good idea. We should focus more on > features. Agreed. Though the article looks quite interesting :) I think that people tend to see nepomuk too much as a kitchen-sink database and are pushing all kinds of junk data into it. Instead of just the data that should be shared with other applications. Cheerio, Ivan -- Money can't buy happiness, but neither can poverty. -- Leo Rosten _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
