You are not logged in.

#1 2015-09-26 13:38:06

tacchinotacchi
Member
Registered: 2014-08-18
Posts: 32

Baloo straight out ignores file index.

Hi.
I can't find a valid alternative (for what i need) to kde, but baloo has been giving me problems for months now.
The documentation is largely absent and the only thing i've left to do is ask for help.
Baloo has always been incredibly slow for me, especially the first queries. After those, some file trees and content are stored in the kernel cache, but it still remains very slow.
To solve this, Baloo normally uses an index file, which i checked and i have in .local/share/baloo/index, 239mb. I also have a file index-lock, 4 kb.
If i do balooctl check behaviour is the same. All files are indexed, the index is just being ignored.
How do I know for sure? I was trying to speed up boot with gopreloader-prepare. And guess what, index doesn't appear in the list.
Thanks in advance for any advice.

Offline

#2 2015-09-26 13:46:29

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 2,313

Re: Baloo straight out ignores file index.

I can't figure out from your post what your problem is. Can you please clarify what you're trying to do, what the expected behavior is and how it fails?

Online

#3 2015-09-26 14:01:33

tacchinotacchi
Member
Registered: 2014-08-18
Posts: 32

Re: Baloo straight out ignores file index.

The problem is that baloo sets up and index, 239 mb, and then doesn't use that. When I make a search query, instead of using the index it reads the huge file tree i have under /home/user, and it takes so long. I checked with gopreload-prepare, which makes a lists of the files accessed by the process, and "index" is not one of them. Even if it wasn't for this, it's so obvious it's not using the index. Let's say I query
baloosearch -d ~/Documents .mp3
Which means search for .mp3 in folder Documents of course.
The first time it takes long (i think around 30 sec )and I can hear the hard drive running fast and the tip skipping over the disk.
From the second time on, since the tree has been saved in the linux cache, it then takes 8 milliseconds to complete the query.
How it fails? Since it got a 239 mb index set up, i'd like it to use it instead of making linux load all the file tree under /home/user

EDIT: tried to clean the cache with sudo sh -c "sync; echo 3 > /proc/sys/vm/drop_caches" and then repeated command. Takes 36 secs again.

Last edited by tacchinotacchi (2015-09-26 14:05:09)

Offline

Board footer

Powered by FluxBB