[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays
From:       <lucke () o2 ! pl>
Date:       2014-05-15 14:17:22
Message-ID: bug-333655-17878-nTgwFNHsud () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #50 from lucke@o2.pl ---
Jonathan, baloo_file_extractor was writing 6-8 MB each second and using 25% of
your cpu time (one core fully in a quad-core?). Later it seems btrfs-delalloc
joined the fun and was using one core almost fully, it continued to run after
baloo_file extractor quit. Only twice your second disk was close to being fully
utilized. An apparently silly baloo_file_extractor behaviour, but is it
something that should trigger a lockup?

You could run "while; do ps ax | grep extractor; sleep 1; done" while trying to
reproduce that baloo_file_extractor activity (lockup), it would give you
numbers of files that extractor was working on, balooshow <numbers> would show
you information about these files - that way you could see what it was trying
to index.

On a related note, I ran baloo_file_extractor on a 20 MB pdf while moving files
between partitions - it normally takes less than 10 s to run, with that disk
activity going on it took 500 s, so idle io class really works.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]