I would love to actually.
I had it removing dangling graphs all the time. But that might have been 
related to a buggy Virtuoso snapshot. Not sure.
Having it in a separate tool - maybe a command line one - would be a 
good idea.

On 06/15/2012 03:18 PM, Vishesh Handa wrote:
> 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
>
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk