[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Activities - Storing ResourceScoreCache in Nepomuk
From: Vishesh Handa <me () vhanda ! in>
Date: 2013-05-22 14:53:48
Message-ID: CAOPTMKBG4U=sY4oMwhPE8B+VnohNsPU6=c1=psnBcVNcq2G1DA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wed, May 22, 2013 at 5:11 PM, Ivan Èukiæ <ivan.cukic@kde.org> wrote:
>
> > Could you please point me to the relevant code?
>
> Quick grep (don't know the code, it is Marco's)
> plasma-mobile/components/metadatamodel/metadatamodel.cpp:411
>
I've checked both the master and integration branch.
I cannot seem to find the file. I did find
plasma-mobile/components/metadatamodel/library/metadatamodel.cpp but that
doesn't seem to use the ResourceScoreCache. Unless I'm missing something.
>
> > Also, why duplicate the data in both the sqlite and nepomuk database?
>
> For the speed issues.*
>
> Storing and querying the desktop events proved to be by an order of
> magnitude
> slower in nepomuk (**for the type of queries that we need**). For that
> reason,
> the sqlite backend was introduced. It freed us from pushing a huge amount
> of
> (for the rest of the world unneeded) data into the database and having to
> query it every time the score is updated.
>
> This way, we are having a private database for private things, and pushing
> only the important data to nepomuk to be accessible by other applications.
> (as IMO it should be in other clients as well - not to abuse a rdf store
> as a
> kitchen-sink database)
>
> Cheerio,
> Ivan
>
> * back then, there were also quite a few thread-safety related issues in
> soprano that kept kamd crashing. But that was not even considered as a
> reason
> for the switch - it was just a nice side-effect to have kamd more stable.
>
> --
> You know, there are many people in the country today who,
> through no fault of their own, are sane. Some of them were born sane.
> Some of them became sane later in their lives...
> -- Monty Python's Flying Circus
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
--
Vishesh Handa
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, \
May 22, 2013 at 5:11 PM, Ivan Čukić <span dir="ltr"><<a \
href="mailto:ivan.cukic@kde.org" target="_blank">ivan.cukic@kde.org</a>></span> \
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div><br> > Could you please point me to the \
relevant code?<br> <br>
</div>Quick grep (don't know the code, it is Marco's)<br>
plasma-mobile/components/metadatamodel/metadatamodel.cpp:411<br></blockquote><div><br></div><div>I've \
checked both the master and integration branch.<br><br></div><div>I cannot seem to \
find the file. I did find \
plasma-mobile/components/metadatamodel/library/metadatamodel.cpp but that doesn't \
seem to use the ResourceScoreCache. Unless I'm missing something.<br> \
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> Also, why duplicate the data in both the sqlite and nepomuk database?<br>
<br>
</div>For the speed issues.*<br>
<br>
Storing and querying the desktop events proved to be by an order of magnitude<br>
slower in nepomuk (**for the type of queries that we need**). For that reason,<br>
the sqlite backend was introduced. It freed us from pushing a huge amount of<br>
(for the rest of the world unneeded) data into the database and having to<br>
query it every time the score is updated.<br>
<br>
This way, we are having a private database for private things, and pushing<br>
only the important data to nepomuk to be accessible by other applications.<br>
(as IMO it should be in other clients as well - not to abuse a rdf store as a<br>
kitchen-sink database)<br>
<br>
Cheerio,<br>
Ivan<br>
<br>
* back then, there were also quite a few thread-safety related issues in<br>
soprano that kept kamd crashing. But that was not even considered as a reason<br>
for the switch - it was just a nice side-effect to have kamd more stable.<br>
<span><font color="#888888"><br>
--<br>
You know, there are many people in the country today who,<br>
through no fault of their own, are sane. Some of them were born sane.<br>
Some of them became sane later in their lives...<br>
-- Monty Python's Flying Circus<br>
</font></span><div><div><br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br><br clear="all"><br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br> </div></div>
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic