Summary: | Add configuration options to allow Baloo to be limited to a certain % CPU / RAM /IO | ||
---|---|---|---|
Product: | [Unmaintained] Baloo | Reporter: | NMD <bugsnmd> |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
NMD
2014-05-13 22:43:40 UTC
Hey Nick. Could you please file a detailed bug about which component is using too much CPU? We have tried to write a simple guide over here - http://community.kde.org/Baloo/Debugging On Wed 14 May 2014 09:47:48 BST, Vishesh Handa wrote: > https://bugs.kde.org/show_bug.cgi?id=334726 > > --- Comment #1 from Vishesh Handa <me@vhanda.in> --- > Hey Nick. > > Could you please file a detailed bug about which component is using too much > CPU? We have tried to write a simple guide over here - > http://community.kde.org/Baloo/Debugging > Hi Vishesh, I'll try and give that a go! Nick Nick, any progress? Hi Christoph, Sorry for the slow reply, I've actually been mostly away from my computer: but the problem hasn't recurred I think. So I'm not sure if the initial problems were just it indexing everything in the first couple weeks of a fresh install? I'm pretty sure the component was baloo_file_extractor. Will look in more detail if it happens again. *** This bug has been marked as a duplicate of bug 333774 *** |