Bug 427819

Summary: Baloo file indexer monopolize most of the resources
Product: [Frameworks and Libraries] frameworks-baloo Reporter: David Abreu <adabreug94>
Component: Baloo File DaemonAssignee: Stefan Brüns <stefan.bruens>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.75.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot with memory details about baloo_indexer

Description David Abreu 2020-10-16 16:35:34 UTC 
Created attachment 132433 [details]
Screenshot with memory details about baloo_indexer

SUMMARY
Baloo file indexer sometimes uses a lot of resources. Maybe could should be a way of giving a default max consumable resources limit for the indexer in order of not stressing the PC with this task in the background, or making it use the resources according to the demand. 

STEPS TO REPRODUCE
1. Download a zipped master branch of any github repo with a considerable size, it happened to me with this repo: https://github.com/mapsme/omim

2. Unzipp it in a directory being watched by baloo

3. Get frozen by douzen of minutes

OBSERVED RESULT
Baloo is taking up to the 40% of the total RAM amount, not even bothering about how much it left avaliable.

EXPECTED RESULT
Baloo should not be taking such an amount of resources. At least not when am actively using other apps in foreground. 

SOFTWARE/OS VERSIONS
 
Linux/KDE Plasma: Neon User 5.20
(available in About System)
KDE Plasma Version: KDE Frameworks Version: 5.20.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
An screenshot have been attached.
Comment 1 David Abreu 2020-10-16 17:05:16 UTC 
By the way, these are my modest resources:

Processors: 4 × Intel® Core™ i3-4170 CPU @ 3.70GHz
Memory: 3.7 GiB of RAM

Graphics Processor: Mesa DRI Intel® HD Graphics 4400
Kernel Version: 5.4.0-51-generic

And I don't have indexing file contet option active
Comment 2 Nate Graham 2020-10-26 19:28:38 UTC 

*** This bug has been marked as a duplicate of bug 394750 ***