[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nepomuk
Subject:    [Nepomuk] Get rid of the Graph Maintainer
From:       Vishesh Handa <me () vhanda ! in>
Date:       2012-06-15 13:30:09
Message-ID: CAOPTMKDXtco3sztQW-TZVOhteH=DzW3+i10Bm_27ZFY_o9iB-Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hey Sebastian

Is it okay if we get rid of the GraphMaintainer in the storage service? It
routinely causes high cpu usage of virtuoso, and I've been getting a lot of
complaints?

What do you think?

Maybe we can move it to a separate Nepomuk Data migration or optimization
application? People can run it if they want, or just the invalid data be.

-- 
Vishesh Handa

[Attachment #5 (text/html)]

Hey Sebastian<br><br>Is it okay if we get rid of the GraphMaintainer in the storage \
service? It routinely causes high cpu usage of virtuoso, and I&#39;ve been getting a \
lot of complaints?<br><br>What do you think?<br><br>Maybe we can move it to a \
separate Nepomuk Data migration or optimization application? People can run it if \
they want, or just the invalid data be.<br clear="all"> <br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br><br>



_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk


[prev in list] [next in list] [prev in thread] [next in thread]