[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Axel Braun]

https://bugs.kde.org/show_bug.cgi?id=333655

--- Comment #74 from Axel Braun  ---
(In reply to Stefan Brüns from comment #73)
> This bug report started with the KDE4 version which still used a Xapian DB.
> 
> Adding comments to it messes up any attempts to pinpoint current issues.
> Please open a new bug report if you have any persisting issues.

Done: https://bugs.kde.org/show_bug.cgi?id=400704

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Stefan Brüns]

https://bugs.kde.org/show_bug.cgi?id=333655

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |MOVED

--- Comment #73 from Stefan Brüns  ---
This bug report started with the KDE4 version which still used a Xapian DB.

Adding comments to it messes up any attempts to pinpoint current issues. Please
open a new bug report if you have any persisting issues.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Axel Braun]

https://bugs.kde.org/show_bug.cgi?id=333655

--- Comment #72 from Axel Braun  ---
PS: I have configured the search to not index the file content. Thats why the
heavy IO surprises me even more

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Axel Braun]

https://bugs.kde.org/show_bug.cgi?id=333655

Axel Braun  changed:

   What|Removed |Added

 CC||axel.br...@gmx.de

--- Comment #71 from Axel Braun  ---
I'm running baloo 5.45.0 on openSUSE Leap 15, and notice that my complete
desktop freezes regularly for 1-2 minutes(!). CPU monitor reports during that
time 100% Load on both cores, but top does not show any process of a
considerable CU load. The problem is more the couple of baloo and akonadi, as
iotop shows:

Total DISK READ :  10.37 M/s | Total DISK WRITE :1060.53 K/s
Actual DISK READ:  10.37 M/s | Actual DISK WRITE: 197.36 K/s
  TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND  
 4497 idle axel9.73 M/s0.00 B/s  0.00 % 99.52 %
baloo_file_extractor
 2847 idle axel  651.54 K/s 1058.15 K/s  0.00 % 97.97 %
akonadi_indexing_agent --identifier akonadi_indexing_agent
   23 be/4 root0.00 B/s0.00 B/s  0.00 %  0.10 % [kworker/1:1]
 2479 be/4 axel0.00 B/s0.00 B/s  0.00 %  0.08 % plasmashell
  849 be/4 root4.76 K/s0.00 B/s  0.00 %  0.00 % [xfsaild/sda2]

(interesting percentage calculation of iotop by the way)

System disk is a SSD, data disk is a hybrid 1TB disk with 8G cache.
Dont know if this is the right bug for this, but it looks like. 
Any idea how to tune/tweak the system to prevent these system freezes?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=333655

joergis...@web.de changed:

   What|Removed |Added

 CC||joergis...@web.de

--- Comment #70 from joergis...@web.de ---
this bug is a duplicate of https://bugs.kde.org/show_bug.cgi?id=332421

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Nick Cross]

https://bugs.kde.org/show_bug.cgi?id=333655

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Mahendra Tallur]

https://bugs.kde.org/show_bug.cgi?id=333655

Mahendra Tallur  changed:

   What|Removed |Added

 CC||ma...@free.fr

--- Comment #69 from Mahendra Tallur  ---
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.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

vigleik.angeltv...@gmail.com changed:

   What|Removed |Added

 CC||vigleik.angeltv...@gmail.co
   ||m

--- Comment #68 from vigleik.angeltv...@gmail.com ---
After upgrading to Kubuntu 16.04 my desktop would also freeze for a few seconds
at random times. In particular it did so every time I ran latex.

I had some trouble tracking down the culprit, but now that I have disabled
Baloo in the system settings my desktop is once again responsive.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Vishesh Handa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

Vishesh Handa  changed:

   What|Removed |Added

   Assignee|m...@vhanda.in|pinak.ah...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Julius Schwartzenberg via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

--- Comment #67 from Julius Schwartzenberg  ---
On Kubuntu 16.04, the system is unusable out of the box with Baloo running.
This appears to be version 5.18. Disabling Baloo allows me to use the system
again.

Maybe Baloo should only run on SSDs?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Mircea Kitsune via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

--- Comment #66 from Mircea Kitsune  ---
Just dropping this here: Yesterday I decided to give another shot to Baloo, so
I re-enabled the desktop search setting. It took Baloo nearly 20 hours to index
everything on my drive! And during this entire day, my system was nearly
unusable: Every process would randomly freeze for several seconds, from any
open application to the desktop itself. I was later told this has to do with
the I/O scheduler, and that Baloo intensively using the drive causes other
processes to have to wait in line.

Whatever the cause, Baloo in its current state is a nightmare... at least if
you have a large home partition (I have nearly 800 GB on mine so yeah). I don't
think any system component made me hate it this way, because of how much it can
mess with your system! At least now that it's indexed everything, things seem
to work alright again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Barney Holmes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

Barney Holmes  changed:

   What|Removed |Added

 CC||djbar...@djbarney.org

--- Comment #65 from Barney Holmes  ---
It should not be aggressive it should be NICE. Talking of which it has the
lowest NICE priority and yet uses 100% of CPU, surely something is wrong there
? But I'm no expert on nice. I had to use "cpulimit" to throttle the process
which helped a bit but still get really annoying GUI freezes. Can someone fix
this please ? To me its a major KDE bug that can ruin the experience for new
users not aware of the indexer and should either be turned OFF by default or
removed. I actually still have it running because I'm curious to see if it does
eventually provided useful search function on my 51GB of user docs and graphics
files and so forth. 

Until then the root of this problem may be in the philosophy of the developers
...

"There is no explicit “Enable/Disable” button any more. We would like to
promote the use of searching and feel that Baloo should never get in the users
way."

http://vhanda.in/blog/2014/04/desktop-search-configuration/

What does "promote the use of searching" mean ? It's up to the user and only
the user what they want or need to use not some "promotion" thing. Also "should
never get in the users way" ... well it does, and really badly as well, this
problem goes back to 2014 and has still not been fixed. What is going on here ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Elián Hanisch via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

Elián Hanisch  changed:

   What|Removed |Added

 CC|lambd...@gmail.com  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Mircea Kitsune via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

Mircea Kitsune  changed:

   What|Removed |Added

 CC||sonichedgehog_hyperblast00@
   ||yahoo.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

[Alexander Potashev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=333655

Alexander Potashev  changed:

   What|Removed |Added

 CC||pinak.ah...@gmail.com
Version|unspecified |5.20.0
Product|Baloo   |frameworks-baloo
  Component|Baloo File Daemon   |Baloo File Daemon

-- 
You are receiving this mail because:
You are watching all bug changes.