Bug 362118

Summary:	Baloo file_extractor slow: 2 MiB pdf is 1.5 h
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	Joe Bramas <htcevo17>
Component:	general	Assignee:	Pinak Ahuja <pinak.ahuja>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aspotashev, pinak.ahuja, stefan.bruens
Priority:	NOR
Version:	5.18.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Joe Bramas 2016-04-23 02:07:48 UTC

baloo is extremely slow to complete
tracker completes in 25 minutes

dpkg --status baloo | egrep "^(V|Pa)"
Package: baloo
Version: 4:5.18.0-0ubuntu1

To restart baloo:
balooctl stop
balooctl enable
- it is unclear what the proper command is
- it will initially chew on the index for 15 minutes before any files are processed

here's a bit of the documentation that is missing:

To see if baloo is running:
X=$(ps -C baloo_file -o pid=) && pstree -pslU $X

To see what file is processed:
X=$(ps -C baloo_file_extractor -o pid=) && sudo lsof -p $X | grep /home

balooshow is unreliable
balooctl config show includeFolders
balooctl config show excludeFolders

System Settings – WorkSpace/Search – File 
use search via Dolphin, click Find, click Content


progress: command takes 30 - 50 s
balooctl status
Baloo File Indexer is running
Indexer state: Idle
Indexed 177982 / 253657 files
Current size of index is 415.12 MiB


Reproducible: Always

Steps to Reproduce:
1. have a pdf in your home directory
2. start baloo
3.

Actual Results:  
using the lsof command, it can be determined that baloo spends at least 1.5 h on a single file

Expected Results:  
baloo to complete in 25 minutes

Comment 1 Stefan Brüns 2018-10-30 17:51:51 UTC

Without the document it is impossible to determine if the content extraction or the database update is responsible for the long processing time.

Please provide the file, if possible.

Comment 2 Bug Janitor Service 2018-11-14 11:33:01 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2018-11-29 09:47:28 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!