https://bugs.kde.org/show_bug.cgi?id=333655
Mahendra Tallur <ma...@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ma...@free.fr
--- Comment #69 from Mahendra Tallur <ma...@free.fr> ---
Hi ! I'm using KDE Neon (latest framework 2.29.0 released yesterday with 4*
baloo write speed improvement - I tried with previous versions too with the
same result).
There is something seriously wrong with Baloo :)
- My laptop is almost 5 year old. It's a decent i5 with a regular HD.
- It's pretty responsible overall when Baloo is disabled
- I made a clean Neon install except for my documents, which I keep
- After 2 hours of initial indexing I noticed my system began to crawl (mouse
pointer would get completely stuck every now & then for up to a minute)
- balooctl status would tell me 140.000 files out of 180.000 were indexed. The
database took less than 2 GB.
- after a whole day of indexing, balooctl status reported only 143.000 files
out of 180.000 and a 5.35 GB index !!
-> the system constantly crawls, the index gets bigger very quick and the
number of indexed files grow very slowly.
Even if I disable baloo, I have to wait for a long time (many mintes) before it
really stops indexing. (sometimes I even have to reboot).
I know indexing is i/o consuming, but it seems something turned wrong when it
reached 140.000 files because it was not THAT slow in the first 2 hours.
What can I do to help ? This is a serious problem IMHO.
Shall I file a new bugreport ? How can I check what are the files currently
being indexed ?
Also, I remember a few months ago when I tried baloo that I had the same issue
and that even after the initial indexing was done (which is not the case now),
downloading some files would cause the PC to crawl because they were being
indexed at the same time.
I love KDE, this is my last remaining issue :-)
Thanks to the community, cheers !
--
You are receiving this mail because:
You are watching all bug changes.
