Got exclude filters (at least in combination with nepomuk).
** Changed in: strigi (Ubuntu)
Status: New => Fix Released
--
strigidaemon needs exclude lists, defaults eat up too many resources
https://bugs.launchpad.net/bugs/137753
You received this bug notification because you are a member
Agree. I tried out Strigi on Gutsy RC, and found that it slows down the
system unacceptably, including foreground processes (re it runs at nice
0). I could imagine someone trying out Kubuntu starting it by mistake
and not knowing why their system was so slow. That would not make a
very good impr
I've been trying to use strigi to index a quite large amount of files eg
around 15 files over 800GB, and all it seems to do is make the
computer completely sluggish! I think that strigi dose not scale very
well to large indexes, and thus is very annoying (for real use).
--
strigidaemon need
Same for me here with Gutsy beta 64 bits on a Core2Duo, 2Gb RAM system.
Strigi slowly eats up CPU% up to 100%, stealing one core for itself and none
else. Thanks for those new dual-core chips otherwise the system will hang on.
But this is not the way it should be. Indexing should start when the
I agree that the default directories to search, include too much. Also
it would be nice if the daemon was running with at nice higher nice
value. That way it would get out of the way when other programs need the
cpu. The high cpu usage btw. makes my Compaq Presario very loud!
--
strigidaemon need
looking at the ~/.strigi/daemon.conf)shows that any file or folder
beggining with a dot will not be indexed, so (in theory) gpothier's
comment shouldn't be true.
CVS folders should be a case of adding:
--
strigidaemon needs exclude lists, defaults eat up too many resources
https://b
Note that by default, strigi also indexes ~/.strigi... that should be on
a exclude list.
--
strigidaemon needs exclude lists, defaults eat up too many resources
https://bugs.launchpad.net/bugs/137753
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Another problem: It clobbers your file-system cache. If you're doing
e.g. development, it is quite common to have your complete source tree
in the kernel filesystem cache, resulting in fast builds. Strigi will
load whatever it is indexing in the fs cache, happily evicting
everything I just recently
