Hi, Yes, I totally understand what nepomuk does... But It never stop interrupt user thread....
Anyway, there is a very old problem (from my memory.. when I really start use nepomuk, I currently using 4.7 beta 1), which is not so critical but annoying. When the nepomuk has hundreds of resource to be remove, like deleting a directory with many files, or deleting thousands of mails from kmail, it always takes a very long time to finish this process. I think it's very easy reproduciable, just simply let nepomuk index a source code folder. When the index is done, delete the folder. >From nepomuk moniter, it takes about tens of seconds to remove only tens of files from nepomuk. If it's not consuming the cpu (only one core, thanks god), even that slow speed is acceptable for me. Is there any way that we can help do address the bug? Like finding the slow sparql statement or so? I think there must already be a(or maybe serveral duplicates) bug report there.. Another thing always confusing me is that virtuoso memory limitation never works? Thanks, Xuetian
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
